Triple
T25131702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monsieur le Président |
E629538
|
entity |
| Predicate | addressedOffice |
P39747
|
FINISHED |
| Object | Président du Sénat |
—
|
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: Président du Sénat | Statement: [Monsieur le Président, addressedOffice, Président du Sénat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressedOffice Context triple: [Monsieur le Président, addressedOffice, Président du Sénat]
-
A.
addressesOffice
Indicates that one entity directs communication, correspondence, or attention specifically to an office associated with another entity.
-
B.
administrativeOffice
chosen
Indicates that one entity serves as the administrative office or central administrative unit responsible for managing or overseeing the affairs of another entity.
-
C.
addressedBy
Indicates that something (such as an issue, request, or item) is handled, dealt with, or responded to by a particular agent or entity.
-
D.
addressing
Indicates that one entity is directing speech, communication, or attention specifically toward another entity.
-
E.
address
Indicates that one entity directs spoken or written communication specifically to another entity.
- 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_69e2ff338250819096ff6c8892804389 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f46d3f35848190b56a4373c97a7d64 |
completed | May 1, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 6:28 a.m.