Triple
T13504664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Havasupai Tribe of the Havasupai Reservation |
E320982
|
entity |
| Predicate | remoteAccess |
P106940
|
FINISHED |
| Object | no road access to Supai |
—
|
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: no road access to Supai | Statement: [Havasupai Tribe of the Havasupai Reservation, remoteAccess, no road access to Supai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remoteAccess Context triple: [Havasupai Tribe of the Havasupai Reservation, remoteAccess, no road access to Supai]
-
A.
supportsRemoteTerminal
Indicates that one entity provides or enables access to another entity via a remote terminal interface.
-
B.
remoteTerminalRole
Indicates that an entity has a specific role or permission level when accessing or operating a system through a remote terminal.
-
C.
remoteArea
chosen
Indicates that an entity is located in or associated with a geographically isolated or sparsely populated area far from urban centers.
-
D.
accessProtocol
Indicates the method or rules by which one entity is allowed to access or communicate with another entity or resource.
-
E.
defaultRemote
Indicates that one entity is designated as the primary or standard remote counterpart used by another entity for communication, synchronization, or access.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf810e248190a060481004503f96 |
completed | April 12, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69dbae0b63748190b5e207f84b2532ea |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:43 p.m.