Triple
T17941021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pătrașcu cel Bun |
E448586
|
entity |
| Predicate | paternityOfMichaelTheBrave |
P46317
|
FINISHED |
| Object | disputed |
—
|
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: disputed | Statement: [Pătrașcu cel Bun, paternityOfMichaelTheBrave, disputed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paternityOfMichaelTheBrave Context triple: [Pătrașcu cel Bun, paternityOfMichaelTheBrave, disputed]
-
A.
hasPossibleFather
chosen
Indicates a relationship where a given individual may be the father of another, but this parentage is not confirmed.
-
B.
claimedFather
Indicates that one entity is asserted or alleged to be the father of another entity, without guaranteeing the claim’s truth.
-
C.
hasOwnerFatherOf
Indicates that the owner of an entity is the father of another specified entity.
-
D.
fatherWas
Indicates that one entity was the male parent (father) of another entity in the past.
-
E.
hasFictionalFather
Indicates that one entity is the fictional father of another 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4ad95f4608190b1ebb45944218f07 |
completed | April 19, 2026, 10:25 a.m. |
| PD | Predicate disambiguation | batch_69e3f8e713d481908b4a126258c18b63 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:21 a.m.