Triple
T25607755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myrmidon |
E641958
|
entity |
| Predicate | hasNotableDescendants |
P17517
|
FINISHED |
| Object | Myrmidons |
—
|
NE NERFINISHED |
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: Myrmidons | Statement: [Myrmidon, hasNotableDescendants, Myrmidons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableDescendants Context triple: [Myrmidon, hasNotableDescendants, Myrmidons]
-
A.
hasNotableDescendant
chosen
Indicates that an entity has at least one descendant who is recognized as notable or significant in some context.
-
B.
hasNotableParent
Indicates that an entity has a parent who is distinguished, prominent, or otherwise notable.
-
C.
hasNotableFieldOfDescendant
Indicates that an entity is associated with a notable field or area of expertise specifically through one or more of its descendants.
-
D.
hasNoDescendants
Indicates that the subject entity does not have any descendants or offspring in the relevant hierarchy or lineage.
-
E.
hasNotableSuccessorType
Indicates that an entity has a successor whose type or category is considered notably significant or distinguished in relation to it.
- 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_69e75dc6ccf081908d49578fd36a76d5 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 21, 2026, 4:39 p.m.