Triple
T319791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stacker Pentecost |
E7787
|
entity |
| Predicate | backstoryDetail |
P4083
|
FINISHED |
| Object | suffers radiation damage from earlier Jaeger piloting |
—
|
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: suffers radiation damage from earlier Jaeger piloting | Statement: [Stacker Pentecost, backstoryDetail, suffers radiation damage from earlier Jaeger piloting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backstoryDetail Context triple: [Stacker Pentecost, backstoryDetail, suffers radiation damage from earlier Jaeger piloting]
-
A.
originStorySummary
Indicates a brief narrative explaining how something began, was created, or came into existence.
-
B.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
C.
lifeDetails
chosen
Indicates that additional information or specific aspects about an entity’s life (such as background, experiences, or personal history) are being described.
-
D.
hasPartInBiography
Indicates that a person or entity is featured or plays a role within someone’s biographical account.
-
E.
subsequentHistory
Indicates that one event, state, or record occurs or is recorded after another in time, reflecting its later historical development or outcome.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea7edbc48190b9031bd1af48f72a |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e946607081909c8b97473aaf8d1b |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.