Triple
T1386366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollodorus of Athens |
E29854
|
entity |
| Predicate | workStatus_OnHomer |
P27240
|
FINISHED |
| Object | lost |
—
|
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: lost | Statement: [Apollodorus of Athens, workStatus_OnHomer, lost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workStatus_OnHomer Context triple: [Apollodorus of Athens, workStatus_OnHomer, lost]
-
A.
worksOver
Indicates that one entity performs work that extends beyond or exceeds a certain limit, threshold, or standard associated with another entity.
-
B.
hooverHomeState
Indicates the state or condition of a home after it has been vacuumed (hoovered).
-
C.
hasWorkBy
Indicates that one entity (such as a collection, exhibition, or publication) includes or contains creative works produced by another entity (such as an artist, author, or creator).
-
D.
workStatusInIsrael
Indicates the employment or legal work authorization status a person holds within Israel.
-
E.
worksThrough
Indicates that one entity performs an action, causes an effect, or achieves a result by using, employing, or acting via another entity as an intermediary or means.
- F. None of above. chosen
Provenance (4 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_69a4befe343c81909f758440a531b5be |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c0335f7081908d50046ced4cdee0 |
completed | March 1, 2026, 10:39 p.m. |
Created at: March 1, 2026, 7:59 p.m.