Triple
T138652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mojave Road historic route |
E2803
|
entity |
| Predicate | originallyUsedBy |
P2834
|
FINISHED |
| Object | Native American tribes |
—
|
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: Native American tribes | Statement: [Mojave Road historic route, originallyUsedBy, Native American tribes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyUsedBy Context triple: [Mojave Road historic route, originallyUsedBy, Native American tribes]
-
A.
historicallyUsedFor
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
-
B.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
-
C.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
-
D.
historicallyBorneBy
chosen
Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
-
E.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
- 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_69a2521e35c08190b28e5c9f1e3c9b59 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a257a800148190be119d1d075869b8 |
completed | Feb. 28, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69a25652efdc8190b85b33735a9e6370 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.