Triple
T31976347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 澜沧江 |
E816457
|
entity |
| Predicate | 相关国际组织 |
P11210
|
FINISHED |
| Object | 湄公河委员会 |
—
|
NE NERFINISHED |
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: 湄公河委员会 | Statement: [澜沧江, 相关国际组织, 湄公河委员会]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 相关国际组织 Context triple: [澜沧江, 相关国际组织, 湄公河委员会]
-
A.
involvedInternationalOrganization
chosen
Indicates that an entity participates in, is affiliated with, or plays a role within an international organization.
-
B.
internationalInstitutionRelationship
Indicates a relationship in which one entity is connected to, interacts with, or is associated with an international institution (such as through membership, partnership, oversight, or collaboration).
-
C.
numberOfInternationalOrganizations
Indicates the quantitative count of international organizations associated with or relevant to a given entity.
-
D.
nearbyInternationalOrganization
Indicates that one entity is located close in distance to an international organization.
-
E.
shareInternationalOrganizationMembership
Indicates that the entities are members of at least one of the same international organization.
- 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_69f348f6a3008190bfb59ca695fd68e2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b344b24881908bf1da55fd9b3a97 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:11 a.m.