Triple
T2300482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comanche |
E51718
|
entity |
| Predicate | forcedOntoReservation |
P38605
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Comanche, forcedOntoReservation, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forcedOntoReservation Context triple: [Comanche, forcedOntoReservation, late 19th century]
-
A.
containsReservation
Indicates that one entity includes or holds a reservation associated with another entity.
-
B.
reservationSystem
Indicates a system or process that manages the creation, modification, and tracking of reservations or bookings between parties.
-
C.
modernReservation
Indicates that an entity is a contemporary or currently active reservation associated with another entity (such as a group, person, or place).
-
D.
reservationPolicy
Indicates the rules or conditions governing how reservations are made, modified, or canceled between parties.
-
E.
reservationLocatedAlong
Indicates that a reservation is situated along, adjacent to, or following the course or extent of a specified linear feature such as a road, river, or boundary.
- 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_69a88b0a9f248190bcff941463d8f65a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abcbabf01081908db3b42bc7c60444 |
completed | March 7, 2026, 6:54 a.m. |
| PD | Predicate disambiguation | batch_69abc58ad33c8190b8d68af41b6f5e07 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abcbab15488190bc8d2345f9d9f2bd |
completed | March 7, 2026, 6:54 a.m. |
Created at: March 4, 2026, 7:49 p.m.