Triple
T31815598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IV Brig Aerotrans |
E812123
|
entity |
| Predicate | logisticsDependence |
P163620
|
FINISHED |
| Object | air logistics |
—
|
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: air logistics | Statement: [IV Brig Aerotrans, logisticsDependence, air logistics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: logisticsDependence Context triple: [IV Brig Aerotrans, logisticsDependence, air logistics]
-
A.
logistics
Indicates the organization, coordination, and management of how resources, goods, or information are efficiently moved and handled between entities.
-
B.
relevanceToLogistics
chosen
Indicates that something has significance, applicability, or impact within logistical processes, planning, or operations.
-
C.
logisticsConcept
Indicates a conceptual or categorical relationship where one entity represents, defines, or is classified as a logistics-related concept for another entity.
-
D.
logisticsFeature
Indicates that something possesses a characteristic, capability, or function specifically related to logistics operations or processes.
-
E.
logisticalEffect
Indicates the impact that one event, action, or condition has on the planning, coordination, or execution of logistical operations.
- 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_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:44 p.m.