Triple
T15902680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Nationalities |
E385627
|
entity |
| Predicate | hasAppointedMembers |
P31811
|
FINISHED |
| Object | 56 |
—
|
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: 56 | Statement: [House of Nationalities, hasAppointedMembers, 56]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAppointedMembers Context triple: [House of Nationalities, hasAppointedMembers, 56]
-
A.
membersAreAppointedIn
Indicates that the members of a group or body are selected or assigned to their positions within a particular organization, institution, or context.
-
B.
hasElectedMembers
Indicates that an entity possesses members who have attained their positions through an election process.
-
C.
membersAppointedFor
Indicates that certain individuals are formally designated to serve as members for a specific body, role, or purpose.
-
D.
includesMembersAppointedBy
Indicates that one entity contains or is composed of members who have been formally appointed by another specified entity.
-
E.
numberOfAppointedMembers
chosen
Indicates the specific count of members who have been formally appointed to a group, body, or position.
- 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142ca3b208190946c3aa4c1e6087c |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:52 a.m.