Triple
T14501324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aaniiih people |
E359643
|
entity |
| Predicate | enteredReservationEra |
P114478
|
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: [Aaniiih people, enteredReservationEra, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredReservationEra Context triple: [Aaniiih people, enteredReservationEra, late 19th century]
-
A.
enteredService
Indicates that an entity began active use or operation at a specific time or in a specific context.
-
B.
hasReservationFor
Indicates that an entity holds or is associated with a reservation for a specific event, service, or resource.
-
C.
containsReservation
Indicates that one entity includes or holds a reservation associated with another entity.
-
D.
reaffirmedAsReservationIn
Indicates that a previously made reservation has been confirmed again as valid or active within a specific context, system, or time frame.
-
E.
modernReservationState
Indicates that an entity is currently in a contemporary or up-to-date state of reservation (e.g., booked, held, or scheduled) according to the modern reservation system.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de94dfe484819086dd971606e6478e |
completed | April 14, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69de5c4ccba08190a988bfda0bc9f5cb |
completed | April 14, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:21 a.m.