Triple
T3617618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parliament of Trinidad and Tobago |
E76639
|
entity |
| Predicate | usesHansard |
P45369
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Parliament of Trinidad and Tobago, usesHansard, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesHansard Context triple: [Parliament of Trinidad and Tobago, usesHansard, yes]
-
A.
hasHansardRecord
chosen
Indicates that there exists an official Hansard (parliamentary debate) transcript or record associated with the given entity.
-
B.
usesParliament
Indicates that one entity conducts its legislative or decision‑making processes through a parliamentary body or system.
-
C.
usedInParliament
Indicates that something (such as a procedure, term, rule, or item) is employed or applied within the context of a parliamentary body or its activities.
-
D.
containsParliament
Indicates that one political or administrative entity includes a parliament within its structure or jurisdiction.
-
E.
parliamentaryResponse
Indicates a formal reply, statement, or action made by a parliamentary body or its members in response to a question, motion, issue, or event.
- 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_69ad85dae2fc81908d1ceadbc6af0089 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc27dd030819083d34fee0c06612a |
completed | March 8, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69adb83f1e4c8190ab501c1c05b14c08 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.