Triple
T36626102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxos |
E904171
|
entity |
| Predicate | timeOfNameUsage |
P59337
|
FINISHED |
| Object | Classical Antiquity |
—
|
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: Classical Antiquity | Statement: [Oxos, timeOfNameUsage, Classical Antiquity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfNameUsage Context triple: [Oxos, timeOfNameUsage, Classical Antiquity]
-
A.
nameUsedSince
Indicates that a particular name has been in use for an entity starting from a specified point in time.
-
B.
timeNamed
Indicates that a specific time or temporal interval is referred to or identified by a particular name or label.
-
C.
usesNameSince
chosen
Indicates that an entity has been using a particular name continuously starting from a specified point in time.
-
D.
incorrectInformalUsageOfName
Indicates that one entity uses another entity’s name in an informal context in a way that is considered incorrect or inappropriate.
-
E.
titleUsedSince
Indicates that a particular title has been in use starting from a specified point in 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe031bc6208190860099aef72d8dcb |
completed | May 8, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69fe014c8b388190b5d4e0cb95ee2be5 |
completed | May 8, 2026, 3:29 p.m. |
Created at: May 3, 2026, 4:11 p.m.