Triple
T18444092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bacchylides |
E450610
|
entity |
| Predicate | workRediscovered |
P37010
|
FINISHED |
| Object | 1896 |
—
|
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: 1896 | Statement: [Bacchylides, workRediscovered, 1896]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workRediscovered Context triple: [Bacchylides, workRediscovered, 1896]
-
A.
wasRediscoveredBy
Indicates that something previously known but lost, forgotten, or overlooked was found or identified again by a particular agent.
-
B.
rediscoveredAt
chosen
Indicates that an entity was found or identified again at a particular time or place after having been lost, forgotten, or unknown.
-
C.
rediscoveredIn
Indicates that something previously known but lost or forgotten was found or identified again at a particular time or place.
-
D.
rediscoveredLiving
Indicates that an entity, once thought lost, extinct, or unknown, has been found or observed alive again.
-
E.
EuropeanRediscoveryLeader
Indicates that the subject was a leading figure in the European rediscovery, exploration, or re-encounter of a place, people, or knowledge previously unknown or forgotten in Europe.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51c142abc8190b4f6f938acdc413d |
completed | April 19, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:30 a.m.