Triple
T1600876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third Committee (Social, Humanitarian and Cultural) |
E34387
|
entity |
| Predicate | typicalMeetingPeriod |
P8280
|
FINISHED |
| Object | October to November |
—
|
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: October to November | Statement: [Third Committee (Social, Humanitarian and Cultural), typicalMeetingPeriod, October to November]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMeetingPeriod Context triple: [Third Committee (Social, Humanitarian and Cultural), typicalMeetingPeriod, October to November]
-
A.
typicalMeetingMonth
Indicates the month in which an entity most commonly or usually holds its meetings.
-
B.
meetingFrequency
Indicates how often a meeting or recurring gathering takes place over a given period.
-
C.
typicalNumberOfMeetingsPerSeason
Indicates the usual or average count of meetings that occur within a single season.
-
D.
typicalSeasonMeetings
chosen
Indicates that there are regularly occurring meetings associated with a particular season or time period.
-
E.
convenesOn
Indicates that an event, group, or body holds a meeting or session at a specific time or date.
- 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_69a885fdcb9c819081ce6f0b8cd477dd |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a95b02cd448190be8e3db9a5a7bac0 |
completed | March 5, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69a907c1cad08190b9728dd557f39aa0 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.