Triple
T7472501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Menominee people |
E176540
|
entity |
| Predicate | reservationEstablished |
P76443
|
FINISHED |
| Object | 1854 |
—
|
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: 1854 | Statement: [Menominee people, reservationEstablished, 1854]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reservationEstablished Context triple: [Menominee people, reservationEstablished, 1854]
-
A.
reservationStatus
Indicates the current state or condition of a reservation within its lifecycle (e.g., pending, confirmed, canceled, completed).
-
B.
reservationSystem
Indicates a system or process that manages the creation, modification, and tracking of reservations or bookings between parties.
-
C.
reservationState
Indicates the current status or phase of a reservation within its lifecycle (e.g., pending, confirmed, canceled, completed).
-
D.
reservationEnclosedBy
Indicates that one reservation is fully contained within the spatial or logical boundaries of another reservation.
-
E.
modernReservation
Indicates that an entity is a contemporary or currently active reservation associated with another entity (such as a group, person, or place).
- 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_69c69f223fd88190b4c69b95d7cbeeda |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f416d018819098275cc51d8def3f |
completed | March 27, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69c6f03d967081908a8e696ff9693b90 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f105e320819091db3cdb1f1351f0 |
completed | March 27, 2026, 9:05 p.m. |
Created at: March 27, 2026, 3:41 p.m.