Triple
T31815610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IV Brig Aerotrans |
E812123
|
entity |
| Predicate | operationalUseCase |
P98789
|
FINISHED |
| Object | crisis response |
—
|
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: crisis response | Statement: [IV Brig Aerotrans, operationalUseCase, crisis response]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalUseCase Context triple: [IV Brig Aerotrans, operationalUseCase, crisis response]
-
A.
operationalService
Indicates that one entity provides, performs, or is responsible for carrying out a particular service or operation for another entity.
-
B.
operationalPurpose
chosen
Indicates the function, role, or intended use that an entity is designed or configured to perform in an operational context.
-
C.
operationOf
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
-
D.
operateIn
Indicates that an entity performs its activities, functions, or services within a specified location, context, or domain.
-
E.
operationalScope
Indicates the range, extent, or boundaries within which an entity, process, or activity is authorized or designed to operate.
- 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ffc89596d08190b97bd60b45c7f9c0 |
completed | May 9, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69ffc81ba5dc8190ae94d44e2284948f |
completed | May 9, 2026, 11:49 p.m. |
Created at: April 30, 2026, 11:44 p.m.