Triple
T35198362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bradley "Rooster" Bradshaw |
E1016329
|
entity |
| Predicate | isSavedBy |
P49226
|
FINISHED |
| Object | Pete "Maverick" Mitchell |
—
|
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: Pete "Maverick" Mitchell | Statement: [Bradley "Rooster" Bradshaw, isSavedBy, Pete "Maverick" Mitchell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSavedBy Context triple: [Bradley "Rooster" Bradshaw, isSavedBy, Pete "Maverick" Mitchell]
-
A.
savedWith
Indicates that one entity is preserved, stored, or kept together in association with another entity.
-
B.
saveBy
chosen
Indicates that one entity preserves, rescues, or protects another entity from loss, harm, or danger.
-
C.
isPreservedBy
Indicates that something remains unchanged, intact, or maintained as it is due to the action or influence of a particular agent or process.
-
D.
savedWhile
Indicates that one entity was saved or preserved during the time another event or action was occurring.
-
E.
savedBecauseOf
Indicates that one entity was preserved, rescued, or kept from loss specifically as a result of another entity’s action, presence, or influence.
- 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_69f76dde814c8190a71f60d514a424a4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78e331ab08190966ad7ec0ec8d846 |
completed | May 3, 2026, 6:04 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.