Triple
T11955306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romania and Ukraine |
E284535
|
entity |
| Predicate | shareCulturalLinks |
P33545
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Romania and Ukraine, shareCulturalLinks, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shareCulturalLinks Context triple: [Romania and Ukraine, shareCulturalLinks, yes]
-
A.
shareCultureWith
chosen
Indicates that two entities mutually participate in, express, or are influenced by the same cultural practices, values, or traditions.
-
B.
sharesCultWith
Indicates that two entities belong to or participate in the same cult or cult-like religious group.
-
C.
culturalElements
Indicates a relationship where certain elements (such as practices, symbols, or artifacts) belong to, express, or characterize a particular culture or cultural context.
-
D.
culturalInterest
Indicates a relationship where one entity has an interest in, appreciation for, or engagement with the culture, traditions, or cultural expressions associated with another entity.
-
E.
culturalExport
Indicates that something originating in one culture is transmitted, adopted, or influential in another culture or region.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90366fda8819083168c93abad27d4 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3e48e08190b2fee43af4f57323 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.