Triple
T24665323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ancient Stratos |
E610657
|
entity |
| Predicate | wasInhabitedUntilCentury |
P50149
|
FINISHED |
| Object | Roman Imperial period |
—
|
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: Roman Imperial period | Statement: [Ancient Stratos, wasInhabitedUntilCentury, Roman Imperial period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasInhabitedUntilCentury Context triple: [Ancient Stratos, wasInhabitedUntilCentury, Roman Imperial period]
-
A.
inhabitedSince
Indicates that a place has been continuously or initially occupied or lived in by someone or something starting from a specified time.
-
B.
settledInCentury
Indicates that an entity’s act of settling or establishment occurred during a specified century.
-
C.
inhabitedDuring
chosen
Indicates that an entity lived in or occupied a place during a specified time period.
-
D.
historicallyInhabitedBy
Indicates that a place or region was inhabited by a particular group or population during some period in the past.
-
E.
colonizedInCentury
Indicates that an entity established a colony or began colonizing another place during a specified century.
- 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_69e2c4d505cc8190981881df06c0bf52 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 2:36 a.m.