Triple
T383851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States airspace |
E8736
|
entity |
| Predicate | extendsOver |
P1673
|
FINISHED |
| Object | United States land territory |
—
|
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: United States land territory | Statement: [United States airspace, extendsOver, United States land territory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extendsOver Context triple: [United States airspace, extendsOver, United States land territory]
-
A.
extendedBy
Indicates that one entity builds upon, enlarges, or adds to the scope, functionality, or duration of another entity.
-
B.
extendsTo
chosen
Indicates that one entity reaches, stretches, or continues its scope, influence, or coverage up to or into another entity.
-
C.
mayExtendTo
Indicates that something has the potential or permission to reach, continue, or be applied up to a specified limit, scope, or boundary.
-
D.
overrides
Indicates that one entity replaces, supersedes, or takes precedence over another in determining the outcome or applicable behavior.
-
E.
expandedBy
Indicates that one entity increases, elaborates, or builds upon the scope, detail, or extent of another entity.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec422b808190b6ddf747ef939151 |
completed | Feb. 28, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69a2e96602188190b0cbc167f55a9237 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.