Triple
T22883516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sylvania |
E567538
|
entity |
| Predicate | hasMediumOfOrigin |
P16967
|
FINISHED |
| Object | cinema |
—
|
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: cinema | Statement: [Sylvania, hasMediumOfOrigin, cinema]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMediumOfOrigin Context triple: [Sylvania, hasMediumOfOrigin, cinema]
-
A.
mediumOfOrigin
chosen
Indicates the original physical or digital medium from which an item, work, or data was derived or obtained.
-
B.
hasTypicalGeographicOrigin
Indicates that an entity is commonly or characteristically associated with originating from a particular geographic location.
-
C.
hasLanguageOfOrigin
Indicates that one entity has its origin or source in the language specified by another entity.
-
D.
speciesOrigin
Indicates the place, environment, or source from which a species originally arose or evolved.
-
E.
hasLikelyOrigin
Indicates that one entity is inferred or believed, with some degree of uncertainty, to be the source or starting point of another entity.
- 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_69e2458a92ec81908fc1cd5f6407d2ab |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17f5dab048190a09c725dad123472 |
completed | April 29, 2026, 3:47 a.m. |
| PD | Predicate disambiguation | batch_69ef3b6b2e2481908258156937b5a745 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:39 p.m.