Triple
T35893008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Histiaeotis |
E1038135
|
entity |
| Predicate | hadStrategicLocation |
P2850
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Histiaeotis, hadStrategicLocation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadStrategicLocation Context triple: [Histiaeotis, hadStrategicLocation, true]
-
A.
strategicLocation
chosen
Indicates that an entity is positioned in a place of particular tactical or strategic importance relative to goals, resources, or other entities.
-
B.
wasStrategicCenterIn
Indicates that an entity functioned as a key strategic center or hub within a specified context, such as a region, period, or conflict.
-
C.
eraOfStrategicImportance
Indicates that a particular time period holds significant strategic value or influence within a broader historical, political, or organizational context.
-
D.
hadLocation
Indicates that an entity was situated at, or associated with, a specific location during a particular time or context.
-
E.
strategicImportanceDueTo
Indicates that one entity possesses strategic significance specifically as a result of its connection, characteristics, or influence related to another entity.
- 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_69f76e2190f88190beb2eed798a4ef01 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa3b4914819098a40400cf7f5b31 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.