Triple
T21567623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Шанхайская пятёрка |
E532201
|
entity |
| Predicate | участникКатегория |
P6384
|
FINISHED |
| Object | государства Азии |
—
|
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: государства Азии | Statement: [Шанхайская пятёрка, участникКатегория, государства Азии]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: участникКатегория Context triple: [Шанхайская пятёрка, участникКатегория, государства Азии]
-
A.
participantFrom
Indicates that a participant originates from, is associated with, or comes out of a specified source, group, or context.
-
B.
participant
Indicates that an entity takes part in, is involved in, or plays a role within a specified event, activity, or process.
-
C.
participantType
chosen
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
-
D.
coParticipantIn
Indicates that two or more entities take part together as participants in the same event, activity, or situation.
-
E.
participantClassification
Indicates how a participant in an event or interaction is categorized or typed with respect to their role or characteristics in that context.
- 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_69e0c460db088190828c64206a450273 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eee9c9f264819085b4807923860793 |
completed | April 27, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:30 p.m.