Triple
T19014213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stari Grad Plain |
E465303
|
entity |
| Predicate | continuityOfUseSince |
P2451
|
FINISHED |
| Object | 4th century BC |
—
|
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: 4th century BC | Statement: [Stari Grad Plain, continuityOfUseSince, 4th century BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuityOfUseSince Context triple: [Stari Grad Plain, continuityOfUseSince, 4th century BC]
-
A.
continuousOwnershipSince
Indicates that one entity has held uninterrupted ownership of another entity or asset starting from a specified point in time.
-
B.
inUseSince
chosen
Indicates that an entity has been actively in use starting from a specified point in time.
-
C.
establishedInContinuity
Indicates that something was created, introduced, or made canonical within the ongoing, in-universe storyline or timeline of a fictional continuity, rather than outside or retroactively.
-
D.
continuityStatus
Indicates the state of whether something continues without interruption or has been broken, paused, or reset over time.
-
E.
usedSince
Indicates that an entity has been in use starting from a specified point in time and continuing thereafter.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6aac4dc8190ac51f22c13f1b96c |
completed | April 20, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.