Triple
T37374355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Big Man |
E927933
|
entity |
| Predicate | characterRaisedBy |
P17573
|
FINISHED |
| Object | Cheyenne |
—
|
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: Cheyenne | Statement: [Little Big Man, characterRaisedBy, Cheyenne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterRaisedBy Context triple: [Little Big Man, characterRaisedBy, Cheyenne]
-
A.
protagonistRaisedBy
Indicates that one entity serves as the primary caregiver or guardian who brings up, nurtures, and looks after the other entity during their formative years.
-
B.
raisedBy
chosen
Indicates that one entity has been brought up, nurtured, or reared under the care, guidance, or authority of another entity.
-
C.
sonRaisedIn
Indicates that a son spent his childhood or formative years being brought up in a particular place or environment.
-
D.
childOfCharacter
Indicates that one character is the offspring (biological, adopted, or otherwise recognized child) of another character.
-
E.
parentOfProtagonistOf
Indicates that one entity is the parent of the main character (protagonist) 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_69f76eb820248190a5c395ca50ad002a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffecdcbac4819093b725a7dbe0e61b |
completed | May 10, 2026, 2:26 a.m. |
| PD | Predicate disambiguation | batch_69ffec3633288190adbbd84e277708dc |
completed | May 10, 2026, 2:23 a.m. |
Created at: May 3, 2026, 4:16 p.m.