Triple
T30097829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir Ector |
E764913
|
entity |
| Predicate | raisedInIgnoranceOfTrueParentage |
P168445
|
FINISHED |
| Object | Arthur |
—
|
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: Arthur | Statement: [Sir Ector, raisedInIgnoranceOfTrueParentage, Arthur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raisedInIgnoranceOfTrueParentage Context triple: [Sir Ector, raisedInIgnoranceOfTrueParentage, Arthur]
-
A.
hasUncertainParentage
Indicates that the parent or parents of an entity are unknown, disputed, or not reliably established.
-
B.
bornWithoutHumanFather
Indicates that an entity is said to have been born without a human biological father.
-
C.
illegitimateChildOf
Indicates that one person is the child of another, but the parent–child relationship is not recognized as lawful or legitimate under the relevant social or legal norms.
-
D.
claimedFather
Indicates that one entity is asserted or alleged to be the father of another entity, without guaranteeing the claim’s truth.
-
E.
hadIllegitimateBirthStatus
Indicates that an entity was born with a socially or legally non-recognized (illegitimate) birth status.
- F. None of above. chosen
Provenance (4 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_69f22474e4288190b5f895fe3974aa92 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67d91ab808190abb9e9748c140161 |
completed | May 2, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 7:07 p.m.