Triple
T9976797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cabinet of New Zealand |
E196350
|
entity |
| Predicate | meetsDay |
P26202
|
FINISHED |
| Object | Monday |
—
|
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: Monday | Statement: [Cabinet of New Zealand, meetsDay, Monday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meetsDay Context triple: [Cabinet of New Zealand, meetsDay, Monday]
-
A.
meetsEvery
Indicates that one entity encounters or comes into contact with every member of a specified set of entities.
-
B.
meetsTo
Indicates that one entity comes together with another at a specific time and place for an encounter, appointment, or interaction.
-
C.
meets
Indicates that two or more entities come together at the same place and time, typically for interaction or a shared purpose.
-
D.
meetsBy
Indicates that one entity encounters or comes together with another entity, typically at a specific time or place.
-
E.
meetingDay
chosen
Indicates the specific day on which a meeting is scheduled or takes place between the related entities.
- 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_69ca82eea2b88190a0e511d21a31f386 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb84d0d3c8190b268582bb79c8973 |
completed | April 2, 2026, 12:29 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9daa808190b413a1b9a1e929e2 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:48 p.m.