Triple
T24401924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tipton Airport |
E615194
|
entity |
| Predicate | located in county |
P23957
|
FINISHED |
| Object | Anne Arundel County |
—
|
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: Anne Arundel County | Statement: [Tipton Airport, located in county, Anne Arundel County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: located in county Context triple: [Tipton Airport, located in county, Anne Arundel County]
-
A.
locatedInCountySeatOfCounty
Indicates that one entity is located in the county seat city or town of the specified county.
-
B.
locatedInCountyRegion
Indicates that one entity is geographically situated within the boundaries of a specific county or county-level region.
-
C.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
D.
inCounty
chosen
Indicates that one entity is geographically or administratively located within the boundaries of a specified county.
-
E.
isInCountySeatOf
Indicates that one entity is located within the town or city that serves as the administrative center (county seat) of a specified county.
- 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.