Triple
T29327493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert de Thibouville |
E743691
|
entity |
| Predicate | hasPaternityStatus |
P149925
|
FINISHED |
| Object | contested |
—
|
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: contested | Statement: [Robert de Thibouville, hasPaternityStatus, contested]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPaternityStatus Context triple: [Robert de Thibouville, hasPaternityStatus, contested]
-
A.
paternalStatus
chosen
Indicates the nature or condition of a paternal relationship that an entity has to another (e.g., being a father, presumed father, or having a specific paternal role or status).
-
B.
paternityConfirmedBy
Indicates that an individual's biological fatherhood of another person has been verified or established by a specified source or method.
-
C.
hasTraditionalFather
Indicates that an entity has a father in the traditional biological or socially recognized paternal sense.
-
D.
hasPossibleFather
Indicates a relationship where a given individual may be the father of another, but this parentage is not confirmed.
-
E.
hasHolderFather
Indicates that an entity has a father who serves as the holder or custodian of that entity.
- 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: April 28, 2026, 1:27 p.m.