Triple
T26766553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syntopicon |
E674954
|
entity |
| Predicate | coversWorksFrom |
P111604
|
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: [Syntopicon, coversWorksFrom, classical antiquity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversWorksFrom Context triple: [Syntopicon, coversWorksFrom, classical antiquity]
-
A.
coverOfWorkBy
Indicates that one work is a cover version or performance of another work originally created by a specified creator or artist.
-
B.
containsWorksFrom
chosen
Indicates that one entity includes or holds works that originate from or are created by another entity.
-
C.
hasWorksAbout
Indicates that one entity (such as a creator, collection, or source) includes or is associated with works whose subject or focus is another entity.
-
D.
worksFrom
Indicates that an entity performs its work or duties starting from or based at a specified location or source.
-
E.
isCoverOf
Indicates that one entity functions as a protective or enclosing layer placed over 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_69eecda85298819097ee1c38a3d772e7 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 27, 2026, 4 a.m.