Triple
T629206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Endeavor Air |
E15887
|
entity |
| Predicate | primaryBusiness |
P11934
|
FINISHED |
| Object | passenger air transport |
—
|
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: passenger air transport | Statement: [Endeavor Air, primaryBusiness, passenger air transport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryBusiness Context triple: [Endeavor Air, primaryBusiness, passenger air transport]
-
A.
businessBase
Indicates that one entity serves as the primary business foundation, core location, or main operational base for another entity.
-
B.
primaryProduct
Indicates that one entity is the main or most important product associated with, produced by, or offered by another entity.
-
C.
primaryService
chosen
Indicates that one entity serves as the main or principal service provided or used in relation to another entity.
-
D.
businessFunction
Indicates the specific role, activity, or operational function that an entity performs within a business context.
-
E.
primaryMode
Indicates the main or most commonly used method, manner, or form in which an action, process, or interaction is carried out between entities.
- 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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e5b5a308190a62165f9275e2f5f |
completed | March 1, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69a49d01b29081908be87e4cd7726ff1 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.