Triple
T10564272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | College of Commissioners |
E249306
|
entity |
| Predicate | hasOneMemberPer |
P94689
|
FINISHED |
| Object | EU member state |
—
|
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: EU member state | Statement: [College of Commissioners, hasOneMemberPer, EU member state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOneMemberPer Context triple: [College of Commissioners, hasOneMemberPer, EU member state]
-
A.
hasOneGovernorPer
Indicates that each instance in the referenced group or category is associated with exactly one governor.
-
B.
hasAssociateMember
Indicates that an entity has another entity connected to it in a non-full, typically limited or secondary, membership capacity.
-
C.
membershipRelationRestrictedTo
Indicates that a membership relationship between entities is limited or constrained to a specified subset, context, or condition.
-
D.
belongsToLine
Indicates that an entity is a member or component of a particular line or linear grouping.
-
E.
hasMembershipBy
Indicates that an entity holds or acquires membership in a group, organization, or program by means of a specified agent, process, or instrument.
- 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d527224b808190b996ae970393f9c3 |
completed | April 7, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69d51901ff6c819095e7b528170a69dc |
completed | April 7, 2026, 2:47 p.m. |
| PDg | Predicate description generation | batch_69d5270eca0481908573b698390c5b08 |
completed | April 7, 2026, 3:47 p.m. |
Created at: April 6, 2026, 12:36 p.m.