Triple
T4473940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metlakatla Indian Community |
E98560
|
entity |
| Predicate | hasReservationStatus |
P56749
|
FINISHED |
| Object | only Native reservation in Alaska |
—
|
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: only Native reservation in Alaska | Statement: [Metlakatla Indian Community, hasReservationStatus, only Native reservation in Alaska]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReservationStatus Context triple: [Metlakatla Indian Community, hasReservationStatus, only Native reservation in Alaska]
-
A.
haveReservation
Indicates that an entity holds or has made a reservation for a service, event, or resource.
-
B.
containsReservation
Indicates that one entity includes or holds a reservation associated with another entity.
-
C.
hasOnlineReservation
Indicates that an entity has a booking or reservation that was made or is managed through an online system.
-
D.
hasReserveStatus
Indicates that an entity holds a designated reserve or backup status in relation to another entity or role.
-
E.
hasReservationType
Indicates that an entity is associated with a specific category or type of reservation.
- F. None of above. chosen
Provenance (4 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_69b3454b4ae481908967426dd37284d6 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35728ed508190ba0e882fa62d8848 |
completed | March 13, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69b3563d63008190816e37027e761375 |
completed | March 13, 2026, 12:11 a.m. |
| PDg | Predicate description generation | batch_69b35727a8ac819090420bd3e2cfbcf1 |
completed | March 13, 2026, 12:15 a.m. |
Created at: March 12, 2026, 11:35 p.m.