Triple
T1630255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jubilee Pass |
E35239
|
entity |
| Predicate | withinRegion |
P9687
|
FINISHED |
| Object | southern Death Valley area |
—
|
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: southern Death Valley area | Statement: [Jubilee Pass, withinRegion, southern Death Valley area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: withinRegion Context triple: [Jubilee Pass, withinRegion, southern Death Valley area]
-
A.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
B.
eligibleRegion
Indicates the geographic area within which something (such as an offer, service, or rule) is valid, applicable, or permitted.
-
C.
territoryIncluded
Indicates that one territory is geographically or administratively contained within another territory.
-
D.
foundInRegion
chosen
Indicates that something is located within, occurs in, or is associated with a specific geographic or spatial region.
-
E.
coreRegionOf
Indicates that one entity constitutes the central or most essential part of another entity’s structure, area, or domain.
- 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_69a886036bc081909ff5de16dbe5e8ea |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9431af5ac8190893133f1ae490142 |
completed | March 5, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69a907c91c888190b6ed295c1a2e0977 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.