Triple
T27573067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Elders |
E696083
|
entity |
| Predicate | memberSource |
P69474
|
FINISHED |
| Object | provincial councils |
—
|
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: provincial councils | Statement: [House of Elders, memberSource, provincial councils]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberSource Context triple: [House of Elders, memberSource, provincial councils]
-
A.
memberFrom
Indicates that an entity is a member originating from, or associated with, a particular source, group, or location.
-
B.
membershipOrigin
chosen
Indicates the source or basis from which an entity’s membership in a group, organization, or category is derived.
-
C.
memberRepresents
Indicates that one entity serves as an official representative or delegate acting on behalf of another entity within a group, organization, or body.
-
D.
memberUnion
Indicates that an entity is a member (part of) a specified union or collective group.
-
E.
membershipField
Indicates that one entity serves as a field or attribute capturing the membership status or association of another entity within a group, organization, or collection.
- 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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 27, 2026, 1:44 p.m.