Triple
T24401931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tipton Airport |
E615194
|
entity |
| Predicate | previously part of |
P29195
|
FINISHED |
| Object | Fort George G. Meade |
—
|
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: Fort George G. Meade | Statement: [Tipton Airport, previously part of, Fort George G. Meade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previously part of Context triple: [Tipton Airport, previously part of, Fort George G. Meade]
-
A.
usedToBePartOf
chosen
Indicates that an entity was formerly a component or member of another entity but is no longer part of it.
-
B.
previouslyPartOfBoundaryBetween
Indicates that something once formed part of the dividing line or border between two areas or entities, but no longer does so.
-
C.
historicallyPartOf
Indicates that one entity was formerly a component, region, or subdivision of another entity during a past historical period, but is not necessarily part of it in the present.
-
D.
formerPartOwnerOf
Indicates that an entity previously held, but no longer holds, a partial ownership stake in another entity.
-
E.
containedPartOf
Indicates that one entity is physically or logically included within and forms a part 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_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.