Triple
T1386369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollodorus of Athens |
E29854
|
entity |
| Predicate | Chronica_form |
P4181
|
FINISHED |
| Object | didactic poem |
—
|
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: didactic poem | Statement: [Apollodorus of Athens, Chronica_form, didactic poem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Chronica_form Context triple: [Apollodorus of Athens, Chronica_form, didactic poem]
-
A.
historicalForm
chosen
Indicates that one entity is an earlier or historically attested form or variant of another entity.
-
B.
chronologicallyClassifiedAs
Indicates that something is assigned to or placed within a specific time period or chronological category.
-
C.
reignCharacterizedBy
Indicates that a ruler’s period of governance is defined or distinguished by a particular quality, condition, or notable feature.
-
D.
historicalScript
Indicates that an entity is or was written in, or otherwise associated with, a particular historical writing system or script.
-
E.
historicalCharacteristic
Indicates that an entity possesses a trait, feature, or quality that is rooted in or defined by its history or past events.
- 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_69a498dc92f8819094a1108f8ac90f43 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c339f3d481909c04b14129899945 |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4beffcf808190ab4cd0271257ce63 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.