Triple
T16595667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | União Nacional |
E403197
|
entity |
| Predicate | restrictedMembership |
P116468
|
FINISHED |
| Object | politically vetted |
—
|
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: politically vetted | Statement: [União Nacional, restrictedMembership, politically vetted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restrictedMembership Context triple: [União Nacional, restrictedMembership, politically vetted]
-
A.
limitedMembershipTo
chosen
Indicates that access, participation, or inclusion in something is restricted to a specific subset of entities or members.
-
B.
membershipRequired
Indicates that access to or use of something is conditional on being a member of a specified group or organization.
-
C.
limitedNumberOfMembers
Indicates that the associated group or entity has a maximum allowed number of members or participants.
-
D.
membershipBased
Indicates that access, participation, or inclusion in something is conditional on holding a membership or belonging to a defined group.
-
E.
membershipIncluded
Indicates that one entity’s membership or inclusion is contained within, or granted as part of, another entity’s membership.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35d717604819083ed60b865bbd13e |
completed | April 18, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69e296a7d9d0819088555bca6c936e79 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:16 a.m.