Triple
T4736747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Priam |
E105142
|
entity |
| Predicate | father |
P120
|
FINISHED |
| Object | Laomedon |
E465476
|
NE 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: Laomedon | Statement: [Priam, father, Laomedon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Laomedon Context triple: [Priam, father, Laomedon]
-
A.
Laomedon
chosen
Laomedon is a legendary king of Troy in Greek mythology, known for his broken promises to gods like Apollo and Poseidon and as the father of Priam.
-
B.
Helinus
Helinus is a small genus of flowering plants known for its climbing or scrambling shrubs, classified within the buckthorn family Rhamnaceae.
-
C.
Telamon
Telamon is a hero in Greek mythology, best known as the father of Ajax the Great and a companion of Heracles in several of his exploits.
-
D.
Peleus
Peleus is a hero in Greek mythology, a king of Phthia and husband of the sea nymph Thetis, best known as the father of Achilles.
-
E.
Priam
Priam is the legendary king of Troy in Greek mythology, best known as the father of Hector and Paris during the Trojan War.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69bd43ee52048190b81a4f066534ffb3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64831c58819098758ac1f7839b3a |
completed | March 20, 2026, 3:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be3a1796608190972865b2f6beef05 |
completed | March 21, 2026, 6:26 a.m. |
Created at: March 20, 2026, 1:19 p.m.