Triple
T26472977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Speaker pro tempore |
E665949
|
entity |
| Predicate | actsInAbsenceOf |
P127541
|
FINISHED |
| Object | Speaker |
—
|
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: Speaker | Statement: [Speaker pro tempore, actsInAbsenceOf, Speaker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actsInAbsenceOf Context triple: [Speaker pro tempore, actsInAbsenceOf, Speaker]
-
A.
notableAbsence
Indicates that something or someone is conspicuously missing from a context where their presence would normally be expected or significant.
-
B.
succeedsInAbsenceOf
Indicates that one entity successfully achieves or maintains something only when another specified entity or condition is not present.
-
C.
actsInSteadOf
chosen
Indicates that one entity performs an action or fulfills a role as a substitute or proxy for another entity.
-
D.
airedAs
Indicates that one media work was broadcast or presented under a particular title, format, or version.
-
E.
declaredDeadInAbsentia
Indicates that an individual has been legally pronounced dead despite their physical absence or lack of a recovered body.
- 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_69ee883f80dc819090e311b022b78e02 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f612ca2eac8190a1b97d0bacd9b20c |
completed | May 2, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 12:21 a.m.