Triple
T36864620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Communal Council of Monaco |
E911036
|
entity |
| Predicate | leaderFunction |
P4351
|
FINISHED |
| Object | presiding officer |
—
|
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: presiding officer | Statement: [Communal Council of Monaco, leaderFunction, presiding officer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leaderFunction Context triple: [Communal Council of Monaco, leaderFunction, presiding officer]
-
A.
leader2
Indicates that one entity serves as a leader, chief, or primary authority figure in relation to another entity.
-
B.
leader5
Indicates that an entity serves as the primary leader, head, or top authority within a specified group, organization, or context.
-
C.
leaderFrom
Indicates that an entity serves or has served as a leader originating from, representing, or associated with a specified place or organization.
-
D.
leaderDuring
Indicates that one entity serves as the leader of another entity during a specified time period.
-
E.
leadingOrgan
chosen
Indicates that one entity serves as the primary or most responsible organizing body or authority for another entity or activity.
- 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_69f76e80f6f0819091cba8e19b269615 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:13 p.m.