Triple
T669848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amphictyonic League |
E12945
|
entity |
| Predicate | territorialFocus |
P8868
|
FINISHED |
| Object | central Greece |
—
|
LITERAL 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: central Greece | Statement: [Amphictyonic League, territorialFocus, central Greece]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: territorialFocus Context triple: [Amphictyonic League, territorialFocus, central Greece]
-
A.
territorialExtent
chosen
Indicates the geographic area or spatial range over which something extends, applies, or has jurisdiction.
-
B.
primaryTerritory
Indicates that a specified area or region is the main or most important territory associated with an entity.
-
C.
deFactoTerritory
Indicates that an area is effectively controlled or administered by an entity in practice, regardless of its official or legal territorial status.
-
D.
expandedTerritoryOf
Indicates that one entity has increased or extended the geographic or jurisdictional area belonging to another entity.
-
E.
territorialDesignation
Indicates that an entity is assigned, defined, or recognized in terms of a specific geographic or territorial area.
- F. None of above.
Provenance (3 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_69a493355dec819098d4244b2fa34885 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49ffbe09881909b547a52a6b34c7f |
completed | March 1, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69a49d18942c819083b3d1887e505900 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.