Triple
T4637288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Mojave Indian Reservation |
E101562
|
entity |
| Predicate | hasHealthcare |
P10262
|
FINISHED |
| Object | tribal health services |
—
|
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: tribal health services | Statement: [Fort Mojave Indian Reservation, hasHealthcare, tribal health services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHealthcare Context triple: [Fort Mojave Indian Reservation, hasHealthcare, tribal health services]
-
A.
hasHealthcareProvider
Indicates that one entity receives healthcare services or medical oversight from another entity acting as its healthcare provider.
-
B.
healthcareType
Indicates the category or kind of healthcare service, system, or coverage associated with an entity.
-
C.
hasMedicalCenter
chosen
Indicates that an entity possesses, hosts, or is associated with a medical center facility.
-
D.
healthSystem
Indicates a relationship where an entity functions as, belongs to, or is managed within a particular health care system or network.
-
E.
hasHealthServicesCoordination
Indicates that one entity is responsible for organizing, managing, or facilitating access to health-related services for another entity.
- 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_69bd43d2f1c081908cd4b7ec48ecc73d |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a62a9e48190b0cf1cbcc51f00c0 |
completed | March 20, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69bd5233cb5081908807e2b150f0ca06 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:13 p.m.