Triple
T29492812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antioch, Tennessee |
E748125
|
entity |
| Predicate | hasHeroicRescuer |
P181325
|
FINISHED |
| Object | James Shaw Jr. |
—
|
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: James Shaw Jr. | Statement: [Antioch, Tennessee, hasHeroicRescuer, James Shaw Jr.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeroicRescuer Context triple: [Antioch, Tennessee, hasHeroicRescuer, James Shaw Jr.]
-
A.
usedMeansToRescue
Indicates that one entity employed a particular method, tool, or means in order to carry out a rescue.
-
B.
seeksToRescue
Indicates an entity’s intention or effort to save or free another entity from danger, harm, or an undesirable situation.
-
C.
hasHeroicResponder
chosen
Indicates that an entity is associated with or supported by another entity that performs a heroic or emergency response action on its behalf.
-
D.
hasRescueTeamCharacter
Indicates that an entity includes or is associated with a character who is part of a rescue team.
-
E.
rescuesWith
Indicates that one entity saves or frees another entity from danger, harm, or captivity using a particular means, tool, or method.
- 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_69f0bd448c6881908aa6b475cefd5ddc |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 28, 2026, 4:15 p.m.