Triple
T4826281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paris |
E107832
|
entity |
| Predicate | father |
P120
|
FINISHED |
| Object | Priam |
E105142
|
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: Priam | Statement: [Paris, father, Priam]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Priam Context triple: [Paris, father, Priam]
-
A.
Priam
chosen
Priam is the legendary king of Troy in Greek mythology, best known as the father of Hector and Paris during the Trojan War.
-
B.
Antenor
Antenor is a wise Trojan elder and counselor in Greek mythology, often portrayed as an advocate for peace during the Trojan War.
-
C.
Helenus
Helenus is a figure in Greek mythology, a Trojan prince and seer known for his prophetic abilities and role in advising both Trojans and Greeks during the Trojan War.
-
D.
Laomedon
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.
-
E.
Diomedon
Diomedon was an Athenian naval commander during the Peloponnesian War, noted for his role in major late-war battles against Sparta.
- 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_69bd43fac8188190803f0327190621e4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6caf22308190a2048ec6acfa5af2 |
completed | March 20, 2026, 3:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be4dcd3ecc8190a5223f00344019ff |
completed | March 21, 2026, 7:50 a.m. |
Created at: March 20, 2026, 1:24 p.m.