Triple
T15850136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heshbon |
E384312
|
entity |
| Predicate | tribalAllocation |
P72912
|
FINISHED |
| Object | tribe of Reuben |
—
|
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: tribe of Reuben | Statement: [Heshbon, tribalAllocation, tribe of Reuben]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tribalAllocation Context triple: [Heshbon, tribalAllocation, tribe of Reuben]
-
A.
allocatedToTribe
chosen
Indicates that something (such as land, resources, or rights) has been formally assigned or designated to a specific tribe.
-
B.
tribalOrganization
Indicates that an entity is organized as, or formally recognized as, a tribal governing or social structure.
-
C.
tribalStatus
Indicates that an entity holds a particular affiliation, recognition, or classification with respect to a tribe or tribal community.
-
D.
tribalCode
Indicates that an entity is governed by, associated with, or identified according to a specific tribal legal or regulatory code.
-
E.
federallyRecognizedTribe
Indicates that the subject is officially acknowledged by the federal government as a Native American tribe with a recognized government-to-government relationship.
- 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142b976c081908d3ba3e705419f3a |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:50 a.m.