Triple
T12278074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rescue Aid Society |
E292642
|
entity |
| Predicate | targetOfRescue |
P860
|
FINISHED |
| Object | children in danger |
—
|
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: children in danger | Statement: [Rescue Aid Society, targetOfRescue, children in danger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetOfRescue Context triple: [Rescue Aid Society, targetOfRescue, children in danger]
-
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.
target
chosen
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
C.
rescuedBy
Indicates that one entity has been saved or brought out of danger by another entity.
-
D.
typeOfRescue
Indicates the specific method or category of rescue operation performed in a rescue event.
-
E.
missionTo
Indicates that one entity is assigned, directed, or sent to carry out a specific mission involving another entity or location.
- 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_69d6ab6856488190b5d31178d5015f8e |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d9380a5e78819086bd4dfe9a83d1f5 |
completed | April 10, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69d91c4a66cc819083ce6fcaf5042af6 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.