Triple
T21589487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Many Farms, Arizona |
E532740
|
entity |
| Predicate | tribalGovernmentServicesCenter |
P11028
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Many Farms, Arizona, tribalGovernmentServicesCenter, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tribalGovernmentServicesCenter Context triple: [Many Farms, Arizona, tribalGovernmentServicesCenter, true]
-
A.
associatedTribalGovernment
Indicates a relationship where an entity is formally linked or connected to a specific tribal government.
-
B.
tribalOrganization
Indicates that an entity is organized as, or formally recognized as, a tribal governing or social structure.
-
C.
tribalHeadquartersOf
Indicates that one location serves as the official headquarters or central administrative base for a particular tribe.
-
D.
governingTribalPresence
Indicates that an entity holds governing authority or administrative control over a tribal presence in a given area or context.
-
E.
governmentCenter
chosen
Indicates that a location serves as the primary administrative or political hub for a government or governing body.
- 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_69e0c46251648190876f0427cf2d321b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eefadb25108190b7a3d2e8dfc8ae60 |
completed | April 27, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69e632109d048190b4ac3f14fe48d1a0 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:32 p.m.