Triple
T3534715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delaware Nation at Moraviantown |
E74742
|
entity |
| Predicate | hasReserveStatus |
P48160
|
FINISHED |
| Object | Indian reserve |
—
|
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: Indian reserve | Statement: [Delaware Nation at Moraviantown, hasReserveStatus, Indian reserve]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReserveStatus Context triple: [Delaware Nation at Moraviantown, hasReserveStatus, Indian reserve]
-
A.
hasReserveFunction
Indicates that an entity serves as a backup or secondary option that can perform the same function if the primary one is unavailable or fails.
-
B.
hasOnlineReservation
Indicates that an entity has a booking or reservation that was made or is managed through an online system.
-
C.
containsReservation
Indicates that one entity includes or holds a reservation associated with another entity.
-
D.
hasReservationType
Indicates that an entity is associated with a specific category or type of reservation.
-
E.
reservationState
Indicates the current status or phase of a reservation within its lifecycle (e.g., pending, confirmed, canceled, completed).
- 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_69ad85d1a3948190931fd1ea1f49717b |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc9cff5c81909011f34c9bf28e11 |
completed | March 8, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69adae13ab808190a5d6ecdc7543445e |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adaed7f2ec819085467d281712e0e8 |
completed | March 8, 2026, 5:16 p.m. |
Created at: March 8, 2026, 3:19 p.m.