Triple
T23225057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rahat |
E580990
|
entity |
| Predicate | hasEvacuationTarget |
P151422
|
FINISHED |
| Object | Indian nationals |
—
|
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: Indian nationals | Statement: [Rahat, hasEvacuationTarget, Indian nationals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEvacuationTarget Context triple: [Rahat, hasEvacuationTarget, Indian nationals]
-
A.
hasEvacuationZone
Indicates that a specified area or location falls within a designated evacuation zone associated with another entity (such as an event, hazard, or authority).
-
B.
hasEvacuationHistory
Indicates that an entity has previously undergone or been involved in one or more evacuation events.
-
C.
evacuatedDuring
Indicates that one entity was removed or relocated from a place or situation during the time period or event represented by the other entity.
-
D.
evacuatedBy
Indicates that an entity is removed or cleared from a place or situation through the action or assistance of another agent or process.
-
E.
evacuationPoint
Indicates a location designated as the place where people should gather or be moved to during an evacuation.
- F. None of above. chosen
Provenance (4 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_69e246043c48819089bae72c9a9c306c |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f1922d30b08190a3c54bab58f5c8e7 |
completed | April 29, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d8770d081908897c28b04e5faea |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 17, 2026, 4:08 p.m.