Triple
T32871870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege Perilous |
E840813
|
entity |
| Predicate | reservedBy |
P4923
|
FINISHED |
| Object | Merlin |
—
|
NE NERFINISHED |
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: Merlin | Statement: [Siege Perilous, reservedBy, Merlin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reservedBy Context triple: [Siege Perilous, reservedBy, Merlin]
-
A.
reservedFor
chosen
Indicates that something is set aside or allocated specifically for the use, benefit, or purpose of a particular entity or group.
-
B.
isReservationOf
Indicates that a given reservation entity is specifically associated with, or made for, a particular resource, service, or event.
-
C.
reservationProvision
Indicates that one entity provides, allocates, or sets aside a reservation (such as a booked resource, service slot, or capacity) for another entity.
-
D.
mayBeReservedBy
Indicates that an entity is eligible or allowed to be reserved by another entity, without asserting that the reservation has actually occurred.
-
E.
reservationIn
Indicates that a reservation is associated with, or booked for, a specific place, service, or resource.
- F. None of above.
Provenance (3 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_69f349436ee88190b72ee12d0f3f508e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:17 a.m.