Triple
T35540375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RMS Carpathia |
E1027042
|
entity |
| Predicate | rescuedPeopleCount |
P8803
|
FINISHED |
| Object | about 705 |
—
|
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: about 705 | Statement: [RMS Carpathia, rescuedPeopleCount, about 705]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rescuedPeopleCount Context triple: [RMS Carpathia, rescuedPeopleCount, about 705]
-
A.
rescuedDuring
Indicates that one entity was rescued in the course of, or as part of, a specified event or time period.
-
B.
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.
-
C.
numberOfRescuers
Indicates the quantity of rescuers involved in or assigned to a particular rescue-related situation or event.
-
D.
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.
-
E.
crewRescued
Indicates that a crew has been successfully saved from danger or a threatening situation.
- 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_69f76e008ba08190927acd8e5e0344c8 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.