Triple
T31100473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Boss |
E792658
|
entity |
| Predicate | geneticFatherOf |
P171144
|
FINISHED |
| Object | Solid Snake |
—
|
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: Solid Snake | Statement: [Big Boss, geneticFatherOf, Solid Snake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geneticFatherOf Context triple: [Big Boss, geneticFatherOf, Solid Snake]
-
A.
hasPossibleFather
Indicates a relationship where a given individual may be the father of another, but this parentage is not confirmed.
-
B.
hasOwnerFatherOf
Indicates that the owner of an entity is the father of another specified entity.
-
C.
forefatherOf
Indicates that one person is an ancestor, typically from an earlier generation, of another person.
-
D.
fatherWas
Indicates that one entity was the male parent (father) of another entity in the past.
-
E.
surrogateFatherOf
Indicates that one entity serves as a surrogate father to another, fulfilling a paternal role without being the biological father.
- 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_69f224cf157c81909e2d2bd88c9282c3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c6e0b888190a417ae712c42db0d |
completed | May 3, 2026, 12:53 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f69c2127088190ae92c72461576d3b |
completed | May 3, 2026, 12:51 a.m. |
Created at: April 29, 2026, 9:03 p.m.