Triple
T23225067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rahat |
E580990
|
entity |
| Predicate | hasOperationNature |
P70163
|
FINISHED |
| Object | non-combatant evacuation operation |
—
|
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: non-combatant evacuation operation | Statement: [Rahat, hasOperationNature, non-combatant evacuation operation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOperationNature Context triple: [Rahat, hasOperationNature, non-combatant evacuation operation]
-
A.
hasOperationType
Indicates the specific kind or category of operation associated with an entity or process.
-
B.
hasOperationsIn
Indicates that an entity conducts business activities or maintains operational presence within a specified location or region.
-
C.
operationalNature
chosen
Indicates the functional or practical manner in which an entity, process, or system operates or carries out its activities.
-
D.
hasBusinessOperation
Indicates that one entity conducts, manages, or is engaged in a commercial or organizational activity involving another entity.
-
E.
hasMainOperations
Indicates that an entity is associated with its primary or core operations, activities, or functions.
- 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_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. |
Created at: April 17, 2026, 4:08 p.m.