Triple
T5848615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing 737 MAX 8 |
E129772
|
entity |
| Predicate | globalGroundingEnd_US |
P66699
|
FINISHED |
| Object | 2020-11 |
—
|
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: 2020-11 | Statement: [Boeing 737 MAX 8, globalGroundingEnd_US, 2020-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: globalGroundingEnd_US Context triple: [Boeing 737 MAX 8, globalGroundingEnd_US, 2020-11]
-
A.
ground
Indicates that one entity is in contact with or supported by the ground or a ground-like surface.
-
B.
locationGroundSegment
Indicates that one entity is located at or associated with a specific ground segment or ground-based infrastructure.
-
C.
groundingEvent
Indicates that an event serves as a foundational or reference occurrence upon which other events, interpretations, or relations are based.
-
D.
groundService
Indicates that one entity provides ground-based operational support or services to another entity, typically in a transportation or logistics context.
-
E.
usesGroundSystem
Indicates that one entity operates, relies on, or interacts with a particular ground-based system to perform its functions or services.
- 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_69c0084bd31c8190a796bb6284845e83 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03c9239e08190bff7ef2bd6d21ae0 |
completed | March 22, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69c0334412388190bc594794ec5754f9 |
completed | March 22, 2026, 6:21 p.m. |
| PDg | Predicate description generation | batch_69c03c8d579081909d7b97fc9014b5d7 |
completed | March 22, 2026, 7:01 p.m. |
Created at: March 22, 2026, 3:55 p.m.