Triple
T282973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G77 |
E5828
|
entity |
| Predicate | hasCurrentNumberOfMembers |
P9078
|
FINISHED |
| Object | over 130 |
—
|
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: over 130 | Statement: [G77, hasCurrentNumberOfMembers, over 130]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCurrentNumberOfMembers Context triple: [G77, hasCurrentNumberOfMembers, over 130]
-
A.
hasMembers
Indicates that a group, organization, or collection includes certain entities as its members.
-
B.
hasMemberCountType
Indicates the type or classification used to describe how the number of members in a group or collection is represented.
-
C.
hasVotingMembers
Indicates that certain entities are recognized as having individuals or units with the authority to vote within a group, body, or decision-making process.
-
D.
hasListOfMembers
Indicates that an entity is associated with a collection containing its members or constituents.
-
E.
hasMemberState
Indicates that an entity includes or comprises another entity as one of its constituent member states within a larger organizational or political structure.
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a25e0c14b48190a5c936bab36180b3 |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b795a6c8190944d48e8418e0ccd |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25c4b773c81908f1017f40b0bfd07 |
completed | Feb. 28, 2026, 3:08 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.