Triple
T21615583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | postYugoslavSpace |
E533425
|
entity |
| Predicate | hasCommonMediaSpace |
P75187
|
FINISHED |
| Object | shared television markets |
—
|
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: shared television markets | Statement: [postYugoslavSpace, hasCommonMediaSpace, shared television markets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonMediaSpace Context triple: [postYugoslavSpace, hasCommonMediaSpace, shared television markets]
-
A.
hasCommonSpace
chosen
Indicates that two or more entities share access to the same physical or virtual area intended for joint or overlapping use.
-
B.
hasCommonMedia
Indicates that two entities share at least one media item (such as an image, video, or audio file) in common.
-
C.
hasCommonElement
Indicates that two sets, collections, or groups share at least one element in common.
-
D.
hasCommonVisualElement
Indicates that two or more entities share at least one similar or identical visual feature or component.
-
E.
hasCommonShape
Indicates that two or more entities share the same or a very similar geometric or visual shape.
- 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_69e0c46411108190bba0d4176dffc9f3 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef3baab9e88190bc02f27133ef32d6 |
completed | April 27, 2026, 10:34 a.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:33 p.m.