Triple
T11713673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Indianapolis |
E278436
|
entity |
| Predicate | survivorsRescued |
P8803
|
FINISHED |
| Object | 316 |
—
|
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: 316 | Statement: [USS Indianapolis, survivorsRescued, 316]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivorsRescued Context triple: [USS Indianapolis, survivorsRescued, 316]
-
A.
rescuedTo
Indicates that one entity has been saved or freed from danger, harm, or a problematic situation and brought to the safety or custody of another entity or location.
-
B.
estimatedNumberOfPeopleSaved
chosen
Indicates the approximate count of individuals whose lives were preserved or harm was averted as a result of a particular action, intervention, or entity.
-
C.
numberOfRescuers
Indicates the quantity of rescuers involved in or assigned to a particular rescue-related situation or event.
-
D.
rescuedBy
Indicates that one entity has been saved or brought out of danger by another entity.
-
E.
usedMeansToRescue
Indicates that one entity employed a particular method, tool, or means in order to carry out a rescue.
- 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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4bf54d88190a8e07fbbf8d9e962 |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7d483081909c2a101087515d74 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.