Triple
T26399055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RSVP-TE |
E663649
|
entity |
| Predicate | canSignal |
P15982
|
FINISHED |
| Object | preemption |
—
|
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: preemption | Statement: [RSVP-TE, canSignal, preemption]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canSignal Context triple: [RSVP-TE, canSignal, preemption]
-
A.
signaled
Indicates that one entity communicated a message, warning, or instruction to another through a deliberate signal or cue.
-
B.
usesSignaling
chosen
Indicates that one entity communicates or coordinates with another by emitting, transmitting, or interpreting signals.
-
C.
sentSignalTo
Indicates that one entity transmitted a signal or message to another entity.
-
D.
canElect
Indicates that one entity has the authority or ability to choose another entity for a position, role, or office through an election process.
-
E.
canSign
Indicates that an entity has the authority or capability to sign a document, agreement, or similar item.
- 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f612607c388190ab61d1ac7d18e08d |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
Created at: April 26, 2026, 11:30 p.m.