Triple
T14184002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teddy Specials (special screenings) |
E351528
|
entity |
| Predicate | isCurated |
P113129
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Teddy Specials (special screenings), isCurated, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCurated Context triple: [Teddy Specials (special screenings), isCurated, true]
-
A.
curatedIn
Indicates that an entity has been intentionally selected, organized, or managed for inclusion within a particular collection, exhibition, or curated context.
-
B.
coCuratedWith
Indicates that two or more entities have been jointly curated or organized together as part of the same curation activity or process.
-
C.
curatedFor
Indicates that something has been selectively organized, chosen, or tailored specifically to suit the needs, interests, or context of a particular target entity.
-
D.
curatedBy
Indicates that something has been selectively organized, managed, or assembled by a particular agent or entity.
-
E.
curatedAt
Indicates the time or context at which an item was intentionally selected, organized, or assembled as part of a curated collection or set.
- F. None of above. chosen
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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61cc0a848190b660095972b1223b |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05baed64819096590e5618a3a8ed |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239a02e881909b0e2679487e4ab2 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 1:03 a.m.