Triple
T445422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Short Parliament |
E7005
|
entity |
| Predicate | languageOfLegislature |
P13286
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Short Parliament, languageOfLegislature, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfLegislature Context triple: [Short Parliament, languageOfLegislature, English]
-
A.
legislature
Indicates that an entity serves as, or is part of, a law-making body or assembly responsible for creating or amending laws for a political unit.
-
B.
legislativeBodyOf
Indicates that one entity is the official legislative body (lawmaking assembly) of another entity, typically a political unit such as a country, state, or city.
-
C.
coLegislatureWith
Indicates that two legislative bodies share lawmaking authority within the same political system or jurisdiction.
-
D.
legislativeChamberLabel
Indicates the official name or label of a legislative chamber within a governmental or parliamentary system.
-
E.
parliamentaryHouse
Indicates that one entity functions as a parliamentary chamber or house within the legislative system of another entity.
- 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_69a2e7e4676c81909ea0dbdecac0687c |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef479ec08190a659eead6eb0d4d0 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2eddfb5508190a4e06e1b260d8b2b |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eeb9e6b0819093863959a6e5730a |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.