Triple
T5700615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theatre of Delos |
E125649
|
entity |
| Predicate | usedInAntiquityBy |
P35749
|
FINISHED |
| Object | inhabitants of Delos |
—
|
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: inhabitants of Delos | Statement: [Theatre of Delos, usedInAntiquityBy, inhabitants of Delos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInAntiquityBy Context triple: [Theatre of Delos, usedInAntiquityBy, inhabitants of Delos]
-
A.
eraUsedIn
Indicates that something (such as a method, standard, or practice) was in active use during a specified historical or temporal era.
-
B.
reputationInAntiquity
Indicates the reputation or standing an entity had during ancient times.
-
C.
historicallyUsedFor
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
-
D.
isAncient
Indicates that the entity existed or originated in a very distant past, typically far earlier than the commonly referenced historical period.
-
E.
traditionallyUsedBy
chosen
Indicates that something has been customarily or historically used by a particular person, group, or culture over time.
- 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_69c0082c96988190b3a6a201edce472a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c024540afc8190aee3760f71ea39c2 |
completed | March 22, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69c021c2d8bc8190b947c7d1f423d2f3 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:45 p.m.