Triple
T1590933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Committee (Disarmament and International Security) |
E34175
|
entity |
| Predicate | sessionStartPeriod |
P302
|
FINISHED |
| Object | Early October |
—
|
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: Early October | Statement: [First Committee (Disarmament and International Security), sessionStartPeriod, Early October]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sessionStartPeriod Context triple: [First Committee (Disarmament and International Security), sessionStartPeriod, Early October]
-
A.
sessionLength
Indicates the duration of time that a particular session lasts from start to end.
-
B.
timePeriod
chosen
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
C.
timeSincePreviousSession
Indicates the amount of time that has elapsed between the current session and the immediately preceding session.
-
D.
locationPeriod
Indicates that an entity is associated with being at a particular location during a specified time period.
-
E.
firstSessionStart
Indicates the point in time when an entity’s very first session or interaction begins.
- 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_69a885fceb2c8190b47e0f7c0aefbff0 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93aedd45c819085843ac843d640e8 |
completed | March 5, 2026, 8:12 a.m. |
| PD | Predicate disambiguation | batch_69a907bdc19081908c84c5c0aa09e282 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:27 p.m.