Triple
T35293504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maximus Air Cargo |
E1019291
|
entity |
| Predicate | subregionOfHeadquarters |
P9956
|
FINISHED |
| Object | Western Asia |
E1091035
|
NE 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: Western Asia | Statement: [Maximus Air Cargo, subregionOfHeadquarters, Western Asia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subregionOfHeadquarters Context triple: [Maximus Air Cargo, subregionOfHeadquarters, Western Asia]
-
A.
subregionOf
chosen
Indicates that one region is geographically or administratively contained within, and is a part of, another larger region.
-
B.
subregionName
Indicates that one region is identified by a specific name used for a smaller or subordinate geographic or administrative area within a larger region.
-
C.
isRegionalSubdivisionOf
Indicates that one region functions as an administrative or geographic subdivision within a larger region.
-
D.
partOfHeadquarters
Indicates that one entity is a component, subdivision, or unit within the headquarters of another entity.
-
E.
originSubregion
Indicates the specific subregional area from which an entity originates or is derived.
- F. None of above.
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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7901ae65c819092f17f92d7b2e561 |
completed | May 3, 2026, 6:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3819e3efcc8190a97b43c36fae4044 |
completed | June 21, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.