Triple
T203214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madam Speaker |
E4551
|
entity |
| Predicate | speechRegister |
P10217
|
FINISHED |
| Object | formal parliamentary language |
—
|
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: formal parliamentary language | Statement: [Madam Speaker, speechRegister, formal parliamentary language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speechRegister Context triple: [Madam Speaker, speechRegister, formal parliamentary language]
-
A.
register
Indicates that an entity formally records or enrolls another entity or itself in an official system, list, or record.
-
B.
speechAct
Indicates that one entity performs a communicative action (such as stating, asking, commanding, or promising) directed toward another entity or audience.
-
C.
spokenForm
Indicates the way something is pronounced or expressed in spoken language, as opposed to its written or symbolic form.
-
D.
recognizedIn
Indicates that an entity is formally acknowledged, honored, or given recognition within a particular context, setting, or domain.
-
E.
spokenBefore
Indicates that one entity has spoken or produced speech earlier in time than another entity.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25f46b4f081909e5ee3718109a71f |
completed | Feb. 28, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69a25b4b42ec8190bef16bbbdd30a742 |
completed | Feb. 28, 2026, 3:04 a.m. |
| PDg | Predicate description generation | batch_69a25f4602c081909e89de233cbc5670 |
completed | Feb. 28, 2026, 3:21 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.