Triple
T21893661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Airport |
E540618
|
entity |
| Predicate | perimeterRuleTypicalLimit |
P14084
|
FINISHED |
| Object | 1250 miles |
—
|
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: 1250 miles | Statement: [National Airport, perimeterRuleTypicalLimit, 1250 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perimeterRuleTypicalLimit Context triple: [National Airport, perimeterRuleTypicalLimit, 1250 miles]
-
A.
perimeterRuleDistanceLimit
chosen
Indicates a constraint that limits how far something may be from a defined perimeter or boundary.
-
B.
typicalBoundary
Indicates that one entity serves as the usual or characteristic boundary or limit for another entity.
-
C.
perimeter
Indicates the total length around the boundary of a two-dimensional shape or region.
-
D.
isLimitOf
Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
-
E.
innerLimit
Indicates a boundary or maximum value that applies within a specified internal or constrained context of 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_69e0c47a95908190ae3e19b716accb3d |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f11fc539708190a42f202e7404a213 |
completed | April 28, 2026, 8:59 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:07 p.m.