Triple
T30211427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spartan–Argive conflicts |
E768075
|
entity |
| Predicate | overTerritory |
P169368
|
FINISHED |
| Object | Cynuria |
—
|
NE NERFINISHED |
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: Cynuria | Statement: [Spartan–Argive conflicts, overTerritory, Cynuria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overTerritory Context triple: [Spartan–Argive conflicts, overTerritory, Cynuria]
-
A.
territoryType
Indicates the specific kind or classification of a territory associated with an entity (e.g., country, region, zone, or jurisdiction type).
-
B.
territoryCorrespondedTo
Indicates that one territory matched, aligned with, or was equivalent to another territory in scope, boundaries, or designation.
-
C.
refersToTerritory
Indicates that one entity designates, mentions, or is associated with a specific geographic area or territorial domain.
-
D.
usesTerritoryFor
Indicates that an entity employs or exploits a particular territory for a specific purpose, function, or activity.
-
E.
mainTerritoryOfInfluence
Indicates the primary geographic area where an entity exerts the most significant control, impact, or influence.
- F. None of above. chosen
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_69f2247eb0848190b4032f302d39c0d9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ff185488190a49b208e4ac6cf59 |
completed | May 2, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 29, 2026, 7:32 p.m.