Triple
T31953529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sokovian |
E815843
|
entity |
| Predicate | relatedToAccords |
P37
|
FINISHED |
| Object | Sokovia Accords |
E234641
|
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: Sokovia Accords | Statement: [Sokovian, relatedToAccords, Sokovia Accords]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToAccords Context triple: [Sokovian, relatedToAccords, Sokovia Accords]
-
A.
relatedTo
chosen
Indicates a general, non-specific relationship or association exists between two entities.
-
B.
relatedToClaimOf
Indicates a relationship where something is connected or pertinent to a specific claim or assertion.
-
C.
associatedThrough
Indicates that two entities are connected or related to each other by means of a specified intermediary, context, or linkage.
-
D.
allyRelation
Indicates a cooperative, supportive relationship in which the entities act as allies toward shared or aligned goals.
-
E.
relatedSuit
Indicates that one suit is associated or connected to another suit in a relevant or meaningful way.
- 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2ed4d917bc8190a8ae452c8843791c |
completed | June 14, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:08 a.m.