Triple
T455265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Clearing Union |
E7218
|
entity |
| Predicate | wouldHaveHadMembers |
P13998
|
FINISHED |
| Object | sovereign states |
—
|
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: sovereign states | Statement: [International Clearing Union, wouldHaveHadMembers, sovereign states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wouldHaveHadMembers Context triple: [International Clearing Union, wouldHaveHadMembers, sovereign states]
-
A.
hadMember
Indicates that an entity was formerly a member or part of another entity or group.
-
B.
hasMembers
Indicates that a group, organization, or collection includes certain entities as its members.
-
C.
formerMemberOf
Indicates that an entity once belonged to or was affiliated with a group, organization, or body, but is no longer a member.
-
D.
hasListOfMembers
Indicates that an entity is associated with a collection containing its members or constituents.
-
E.
laterMember
Indicates that one entity became a member of a group or organization at a later time than another entity.
- 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef9f772c8190863399c5ee1378fe |
completed | Feb. 28, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69a2ede4de008190b5a6c159e741522e |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eeeb85f881909580a6a86332b4a5 |
completed | Feb. 28, 2026, 1:34 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.