Triple
T25143230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Big Leap |
E629860
|
entity |
| Predicate | mainCharacterFocus |
P77485
|
FINISHED |
| Object | group of underdogs |
—
|
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: group of underdogs | Statement: [The Big Leap, mainCharacterFocus, group of underdogs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCharacterFocus Context triple: [The Big Leap, mainCharacterFocus, group of underdogs]
-
A.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
B.
mainProtagonistHome
Indicates the primary residence or home location associated with the main protagonist in a narrative or work.
-
C.
mainMortalCharacter
Indicates that the referenced entity serves as the primary mortal (non-immortal) character in the context of a story or narrative.
-
D.
characterInFocus
chosen
Indicates that a particular character is the primary subject or focal point within a given context, scene, or narrative segment.
-
E.
mainCharacterCodeNumber
Indicates that an entity is identified as the primary or central character by a specific code number.
- 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_69e2ff349e408190a6f4a5a66279f54d |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f4684a765c819091891c99ed64a7e7 |
completed | May 1, 2026, 8:46 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:29 a.m.