Triple
T35040745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regional Cooperation for Development |
E1011061
|
entity |
| Predicate | collaborationField |
P26572
|
FINISHED |
| Object | trade |
—
|
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: trade | Statement: [Regional Cooperation for Development, collaborationField, trade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collaborationField Context triple: [Regional Cooperation for Development, collaborationField, trade]
-
A.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
-
B.
collaborationAspect
Indicates a specific characteristic, dimension, or feature of how entities collaborate or work together.
-
C.
collaborationArea
chosen
Indicates the domain, topic, or field in which two or more entities work together or collaborate.
-
D.
collaborativeWork
Indicates a relationship where two or more entities jointly contribute effort or resources toward a shared task, project, or goal.
-
E.
collaboratesVia
Indicates that two or more entities work together or coordinate their activities through a specified medium, channel, or intermediary.
- 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_69f76dcea02c81908542a223f6d5059f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.