Triple
T26495923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIDA |
E669280
|
entity |
| Predicate | isParliamentary |
P68852
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [FIDA, isParliamentary, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isParliamentary Context triple: [FIDA, isParliamentary, true]
-
A.
parliamentary
chosen
Indicates that an entity is related to, governed by, or characteristic of a parliamentary system, institution, or process.
-
B.
parliamentaryStatus
Indicates the relationship of whether and how an entity is formally recognized or holds standing within a parliamentary system or body.
-
C.
isParliamentarySegmentOf
Indicates that one entity is a specific segment, session, or portion within the proceedings or structure of a parliamentary body of another entity.
-
D.
isSovereignParliament
Indicates that a parliament holds ultimate legislative authority within its jurisdiction, not legally constrained by any higher lawmaking body.
-
E.
ParliamentarianSide
Indicates that one entity is aligned with, represents, or belongs to the Parliamentarian side in a political or legislative context.
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 27, 2026, 1:08 a.m.