Triple
T6932148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miguel Hidalgo y Costilla Guadalajara International Airport |
E160460
|
entity |
| Predicate | hasPublicUse |
P30373
|
FINISHED |
| Object | civil |
—
|
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: civil | Statement: [Miguel Hidalgo y Costilla Guadalajara International Airport, hasPublicUse, civil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicUse Context triple: [Miguel Hidalgo y Costilla Guadalajara International Airport, hasPublicUse, civil]
-
A.
hasPublic
Indicates that an entity is accessible or visible to the general public rather than being private or restricted.
-
B.
isPubliclyAccessible
chosen
Indicates that the referenced entity can be accessed or used by the general public without special permissions or restrictions.
-
C.
hasOfficialUse
Indicates that something is used in an authorized or formally recognized capacity, typically by an official body or for official purposes.
-
D.
isPrivateOrPublic
Indicates whether something is designated as private or public in terms of its accessibility or visibility.
-
E.
hasHumanUse
Indicates that something is used, employed, or utilized by humans for a particular purpose or benefit.
- 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_69c6884e15208190b9e91487eaafcf85 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6da3e58f08190857c14f538448039 |
completed | March 27, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bb577c81908ee8b415b4281f3d |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:27 p.m.