Triple
T698260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of Ministers of France |
E13940
|
entity |
| Predicate | usualMeetingDay |
P13719
|
FINISHED |
| Object | Wednesday |
—
|
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: Wednesday | Statement: [Council of Ministers of France, usualMeetingDay, Wednesday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usualMeetingDay Context triple: [Council of Ministers of France, usualMeetingDay, Wednesday]
-
A.
designatedDayFor
chosen
Indicates that a specific day is officially assigned or reserved for a particular purpose, event, or activity.
-
B.
typicalMeetingMonth
Indicates the month in which an entity most commonly or usually holds its meetings.
-
C.
convenesIn
Indicates that an entity brings together or assembles a group, meeting, or event at a specific place or venue.
-
D.
usesCalendar
Indicates that an entity employs or relies on a calendar system for organizing, tracking, or scheduling dates and events.
-
E.
mayMeet
Indicates that one entity is permitted or has the possibility to meet or come together with 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a0c99be48190babc37c397b6a186 |
completed | March 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69a49d2586b081908e052cc5ba1d2685 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.