Triple
T4956422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polynices |
E111290
|
entity |
| Predicate | parentalLineage |
P36142
|
FINISHED |
| Object | descendant of the Labdacids |
—
|
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: descendant of the Labdacids | Statement: [Polynices, parentalLineage, descendant of the Labdacids]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentalLineage Context triple: [Polynices, parentalLineage, descendant of the Labdacids]
-
A.
genealogicalLine
chosen
Indicates a genealogical relationship connecting individuals through lines of descent or ancestry.
-
B.
patriarchalLineage
Indicates a familial relationship where descent, inheritance, or identity is traced through the male line or father’s ancestry.
-
C.
parentageVariant
Indicates a relationship where one entity is a variant or alternative form of another entity’s parentage or parental assignment.
-
D.
parentageIncludes
Indicates that a given parentage or lineage set contains or encompasses a particular parent or ancestral relationship.
-
E.
parentageInSomeSources
Indicates that a parental relationship between entities is reported or asserted in some, but not necessarily all, available sources.
- 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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd71d6ba9c8190932f8d81240c3f56 |
completed | March 20, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3beb008190852fd6150813b252 |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:32 p.m.