Triple
T26747888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sundowner |
E674451
|
entity |
| Predicate | rescueRole |
P137240
|
FINISHED |
| Object | evacuation of Allied troops from France |
—
|
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: evacuation of Allied troops from France | Statement: [Sundowner, rescueRole, evacuation of Allied troops from France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rescueRole Context triple: [Sundowner, rescueRole, evacuation of Allied troops from France]
-
A.
roleInRescue
chosen
Indicates the specific function or responsibility an entity has within a rescue operation or event.
-
B.
questRole
Indicates the specific function or part an entity plays within a quest or mission.
-
C.
sonRole
Indicates that one entity holds the role or relationship of a son with respect to another entity.
-
D.
seeksToRescue
Indicates an entity’s intention or effort to save or free another entity from danger, harm, or an undesirable situation.
-
E.
rescueCoordinatedBy
Indicates that a rescue operation is organized, directed, or managed by a particular coordinating entity.
- 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_69eecda63a3881908095c47900692e65 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61886fd78819096f521fd8b9b1092 |
completed | May 2, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:52 a.m.