Triple
T35475277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Poachers |
E1025313
|
entity |
| Predicate | hasRegionalTiesTo |
P31610
|
FINISHED |
| Object | East of England |
E7736
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: East of England | Statement: [The Poachers, hasRegionalTiesTo, East of England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionalTiesTo Context triple: [The Poachers, hasRegionalTiesTo, East of England]
-
A.
hasTerritorialAssociation
Indicates a relationship where an entity is linked or connected to a specific territory, area, or geographic region.
-
B.
hasRegionalInfluenceFrom
Indicates that one entity’s influence, impact, or authority in a region is derived from or shaped by another entity.
-
C.
hasRegionalEntity
Indicates that one entity includes, governs, or is associated with another entity that functions as its regional subdivision or component.
-
D.
hasGeographicConnectionTo
Indicates a relationship where two entities are linked through a shared or relevant geographic feature, location, or spatial association.
-
E.
hasRegionalAffiliation
chosen
Indicates that an entity is associated with, belongs to, or is officially linked to a specific geographic region.
- F. None of above.
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38403ba6808190bd62e228cc5d827f |
completed | June 21, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:04 p.m.