Triple
T16289184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papago |
E395471
|
entity |
| Predicate | notableReservationFeature |
P122547
|
FINISHED |
| Object | shares border with Mexico |
—
|
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: shares border with Mexico | Statement: [Papago, notableReservationFeature, shares border with Mexico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableReservationFeature Context triple: [Papago, notableReservationFeature, shares border with Mexico]
-
A.
notableReservation
Indicates that an entity has a reservation or booking that is significant, prominent, or otherwise noteworthy in context.
-
B.
notableResort
Indicates that a location functions as a resort that is recognized for its significance, prominence, or special reputation.
-
C.
notableFeatureOn
Indicates that one entity is a prominent or distinguishing feature located on or part of another entity.
-
D.
amenitiesInclude
Indicates that a place or facility provides or contains specific amenities as part of its features.
-
E.
reservationAlsoKnownAs
Indicates that a reservation is referred to by an alternative name or alias.
- F. None of above. chosen
Provenance (4 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e249175e24819082e571039e278056 |
completed | April 17, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:05 a.m.