Triple
T3949253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of 1933 |
E84822
|
entity |
| Predicate | limitedInstitution |
P53069
|
FINISHED |
| Object | parliament |
—
|
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: parliament | Statement: [Constitution of 1933, limitedInstitution, parliament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: limitedInstitution Context triple: [Constitution of 1933, limitedInstitution, parliament]
-
A.
grantedByInstitution
Indicates that something (such as a status, permission, or resource) is conferred or authorized by an institution.
-
B.
usedByInstitution
Indicates that something (such as a resource, tool, or method) is utilized or employed by an institution.
-
C.
eligibleInstitution
Indicates that an institution satisfies specified criteria or requirements to qualify for a particular program, benefit, or status.
-
D.
hasLocalInstitution
Indicates that a given place or region possesses or hosts an institution that operates locally within its boundaries.
-
E.
establishedInstitution
Indicates that an entity founded, created, or formally set up an institution or organization.
- F. None of above. chosen
Provenance (4 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_69aed934fbfc8190847068e4546de963 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaa5afdc8190b709af2473d75d02 |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8ed04e4819096bced8971cd888d |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefaa3c6a08190bfe76629c7c98eea |
completed | March 9, 2026, 4:51 p.m. |
Created at: March 9, 2026, 3:30 p.m.