Triple
T27005579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mookie Wilson |
E680231
|
entity |
| Predicate | relationshipToPrestonWilson |
P199338
|
FINISHED |
| Object | stepfather |
—
|
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: stepfather | Statement: [Mookie Wilson, relationshipToPrestonWilson, stepfather]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToPrestonWilson Context triple: [Mookie Wilson, relationshipToPrestonWilson, stepfather]
-
A.
relationshipToGeorgeWilson
Indicates the specific nature of the relationship or connection that an entity has to George Wilson.
-
B.
worksInCloseRelationshipWith
Indicates a collaborative professional relationship in which two or more entities work together closely and interact frequently to achieve shared goals.
-
C.
relationshipToPavelVlasov
Indicates the nature or type of relationship an entity has with Pavel Vlasov.
-
D.
relationshipToBenWhittaker
Indicates the specific nature of the relationship an entity has with Ben Whittaker.
-
E.
relationshipToWalterBurns
Indicates the specific nature of the relationship an entity has with Walter Burns, such as familial, professional, or social connection.
- 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_69eeeb53939c8190bd431f32b060f01f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69ff2fbae9b48190847eefa1c227d43e |
completed | May 9, 2026, 12:59 p.m. |
| PD | Predicate disambiguation | batch_69ff2f2218048190a32224a648182b5d |
completed | May 9, 2026, 12:57 p.m. |
| PDg | Predicate description generation | batch_69ff2fb9e46c8190b36b3e0bc84f114c |
completed | May 9, 2026, 12:59 p.m. |
Created at: April 27, 2026, 7 a.m.