Triple
T6663561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saddle Peak National Park |
E151536
|
entity |
| Predicate | nearestCountryMainland |
P7310
|
FINISHED |
| Object | India mainland |
—
|
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: India mainland | Statement: [Saddle Peak National Park, nearestCountryMainland, India mainland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestCountryMainland Context triple: [Saddle Peak National Park, nearestCountryMainland, India mainland]
-
A.
nearestMainlandPoint
Indicates the relationship where a location is associated with the closest point on the mainland to that location.
-
B.
countryClosestTo
chosen
Indicates the relationship where one country is geographically nearer to a given reference point or entity than any other country.
-
C.
nearestLandmass
Indicates that one landmass is the closest geographically to another specified point or landmass.
-
D.
nearestMainlandState
Indicates the relationship where a given location is associated with the closest U.S. mainland state in terms of geographic proximity.
-
E.
geographicallyAdjacentTo
Indicates that two geographic entities share a common boundary or are directly next to each other in space.
- 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_69c687f5fac48190a09e4838d9c6b45d |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9d53848190ac75523c157249c6 |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad071b0081909b96dd4b93414bd1 |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:02 p.m.