Triple
T17711424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | proceedings of the New Zealand House of Representatives |
E441574
|
entity |
| Predicate | occurDuring |
P3824
|
FINISHED |
| Object | sittings of the House |
—
|
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: sittings of the House | Statement: [proceedings of the New Zealand House of Representatives, occurDuring, sittings of the House]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occurDuring Context triple: [proceedings of the New Zealand House of Representatives, occurDuring, sittings of the House]
-
A.
occurredDuring
chosen
Indicates that one event or action took place within the temporal span of another event or time period.
-
B.
occursWhen
Indicates that one event or condition happens at the same time or is triggered under the circumstances defined by another event or condition.
-
C.
occurredBetween
Indicates that an event or action took place within the time interval defined by two temporal boundaries.
-
D.
occursAt
Indicates that an event or action takes place at a specific time or location.
-
E.
executedDuring
Indicates that an action or event was carried out within the temporal span of another specified event or period.
- 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4729b5d3c819085613ed25dc6761d |
completed | April 19, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69e3cde601d4819097903f471f1fe99a |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:05 a.m.