Triple
T21497036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Yavapai |
E530381
|
entity |
| Predicate | laterReturnTo |
P45021
|
FINISHED |
| Object | central Arizona homelands |
—
|
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: central Arizona homelands | Statement: [Western Yavapai, laterReturnTo, central Arizona homelands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterReturnTo Context triple: [Western Yavapai, laterReturnTo, central Arizona homelands]
-
A.
returnsTo
chosen
Indicates that an entity goes back to a previous location, state, or entity it was associated with before.
-
B.
laterLocation
Indicates that an entity is located at a specified place at a later time than some reference time or earlier location.
-
C.
forcedToReturnTo
Indicates that one entity is compelled, against its preference or by external pressure or requirement, to go back to a previous place, state, or situation.
-
D.
laterWithin
Indicates that one event or time point occurs later than another while still falling within a specified temporal interval or boundary.
-
E.
returnedFrom
Indicates that an entity has come back or been sent back from a specified source, location, or prior state.
- 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_69e0c45bd15481909fba5910765cdda2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea58faa08190ab9f60b0db3c425b |
completed | April 23, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:23 p.m.