Triple
T3017199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enrich |
E82364
|
entity |
| Predicate | tierQualificationBasis |
P7476
|
FINISHED |
| Object | flight activity |
—
|
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: flight activity | Statement: [Enrich, tierQualificationBasis, flight activity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tierQualificationBasis Context triple: [Enrich, tierQualificationBasis, flight activity]
-
A.
eligibilityLevel
Indicates the degree or tier of qualification an entity has for a given benefit, service, or status.
-
B.
eligibilityCategory
Indicates the classification or type of eligibility that applies to an entity within a given context.
-
C.
rankingBasis
chosen
Indicates the criterion or standard used to determine the order or rank of entities in a ranking.
-
D.
eligibilityCriteria
Indicates the conditions or requirements that must be satisfied for an entity to qualify for or be considered eligible for something.
-
E.
eligibility
Indicates that an entity meets the required conditions or qualifications to participate in, receive, or perform something.
- 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_69ad8b1eb53481908c39bbcd1ec104b2 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a6c56708190b7d8d08bca727cc1 |
completed | March 8, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69ad961a97188190809dc73430a8eda8 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.