Triple
T5363634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orestheus |
E103077
|
entity |
| Predicate | hasParentageType |
P32523
|
FINISHED |
| Object | mortal or semi-legendary human lineage |
—
|
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: mortal or semi-legendary human lineage | Statement: [Orestheus, hasParentageType, mortal or semi-legendary human lineage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentageType Context triple: [Orestheus, hasParentageType, mortal or semi-legendary human lineage]
-
A.
parentageIncludes
chosen
Indicates that a given parentage or lineage set contains or encompasses a particular parent or ancestral relationship.
-
B.
isParentOf
Indicates that one entity is the biological or legal parent of another entity.
-
C.
hasParentCharacter
Indicates that one character is the parent of another character.
-
D.
hasParentCompanyType
Indicates that an entity is associated with a parent company of a specified organizational or business type.
-
E.
hasParentCategory
Indicates that an entity belongs to or is organized under a broader, more general category.
- 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_69bd43daa3e4819090b59d127db70e57 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd865d42508190a1a96121674c1020 |
completed | March 20, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69bd845f41f88190b75b8b64b9e41862 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:02 p.m.