Triple
T24401923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tipton Airport |
E615194
|
entity |
| Predicate | owned by |
P347
|
FINISHED |
| Object | Tipton Airport Authority |
—
|
NE NERFINISHED |
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: Tipton Airport Authority | Statement: [Tipton Airport, owned by, Tipton Airport Authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: owned by Context triple: [Tipton Airport, owned by, Tipton Airport Authority]
-
A.
ownedBy
chosen
Indicates that one entity possesses legal or rightful ownership of another entity.
-
B.
ownedIn
Indicates that one entity possesses or holds legal or recognized ownership of another entity within a specific context, domain, or scope.
-
C.
typicallyOwnedBy
Indicates that something is most commonly or usually possessed or owned by a particular type of entity.
-
D.
ownedMostlyBy
Indicates that one entity holds the majority ownership or controlling share of another entity.
-
E.
ownershipBasedIn
Indicates that an entity’s ownership or controlling stake is primarily located, registered, or based in a particular place or jurisdiction.
- 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_69e2d7e780bc81908049c779e697a7f6 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f294db57248190b6f836269248b781 |
completed | April 29, 2026, 11:31 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:05 a.m.