Triple
T36803670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States–Montenegro relations |
E909386
|
entity |
| Predicate | supportedMembershipIn |
P13222
|
FINISHED |
| Object | NATO |
E341
|
NE 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: NATO | Statement: [United States–Montenegro relations, supportedMembershipIn, NATO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedMembershipIn Context triple: [United States–Montenegro relations, supportedMembershipIn, NATO]
-
A.
supportsMembersOf
Indicates that one entity provides assistance, backing, or advocacy specifically to the members of another entity or group.
-
B.
membershipIn
Indicates that an entity belongs to, is part of, or holds membership in a particular group, organization, or collection.
-
C.
supportedClub
Indicates that one entity has given their backing, endorsement, or assistance to a particular club.
-
D.
supportsOrganization
chosen
Indicates that one entity provides assistance, resources, or advocacy that helps sustain or advance an organization.
-
E.
eligibleMembers
Indicates that certain entities meet the required criteria or conditions to be considered eligible members of a specified group or category.
- F. None of above.
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_69f76e7b98888190899b6478a82ad6ae |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3d17b20bac8190bb73387ece847ddd |
completed | June 25, 2026, 11:57 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.