Triple
T32797027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People’s Councils in Vietnam |
E838792
|
entity |
| Predicate | haveMembersCalled |
P6049
|
FINISHED |
| Object | deputies to People’s Council |
—
|
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: deputies to People’s Council | Statement: [People’s Councils in Vietnam, haveMembersCalled, deputies to People’s Council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveMembersCalled Context triple: [People’s Councils in Vietnam, haveMembersCalled, deputies to People’s Council]
-
A.
membersCalled
chosen
Indicates that specific members of a group or collection are being referred to or identified by a particular name or label.
-
B.
hasMembers
Indicates that a group, organization, or collection includes certain entities as its members.
-
C.
hasMembersWith
Indicates that a group or collection includes one or more specific members that satisfy a given condition or characteristic.
-
D.
hasCall
Indicates that one entity initiates or participates in a telephone or voice communication with another entity.
-
E.
hasMemberFromEach
Indicates that a group or collection includes at least one member originating from each specified category, set, or subgroup.
- 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_69f3493c7f6881908edf2aa13631d1e0 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:14 a.m.