Triple
T13689532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palácio da Horta |
E328223
|
entity |
| Predicate | parliamentTypeServed |
P75281
|
FINISHED |
| Object | regional 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: regional parliament | Statement: [Palácio da Horta, parliamentTypeServed, regional parliament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parliamentTypeServed Context triple: [Palácio da Horta, parliamentTypeServed, regional parliament]
-
A.
legislatureTypeServed
chosen
Indicates the type of legislative body in which an entity has served (e.g., national, state, or local legislature).
-
B.
servedInParliament
Indicates that a person has held a position as a member of a parliamentary body during some period of time.
-
C.
servedInParliamentFor
Indicates that a person held a parliamentary seat as a representative of a specified constituency, region, or jurisdiction.
-
D.
legislativeChamberServed
Indicates that an individual has served as a member of a specified legislative chamber.
-
E.
legislatureServed
Indicates that an individual has served as a member of a specific legislative body during some period of time.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc6721c248190ac48491b5f39c8f0 |
completed | April 12, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:53 p.m.