Triple
T19272054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star Wars opening crawl |
E481952
|
entity |
| Predicate | laterTechnique |
P104064
|
FINISHED |
| Object | digital visual effects |
—
|
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: digital visual effects | Statement: [Star Wars opening crawl, laterTechnique, digital visual effects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterTechnique Context triple: [Star Wars opening crawl, laterTechnique, digital visual effects]
-
A.
specialEffectsTechnique
chosen
Indicates a relationship where a particular special effects method or process is used to create or enhance visual or auditory effects in a production.
-
B.
laterLighting
Indicates that one lighting event or condition occurs after another in time.
-
C.
laterUsedTechnology
Indicates that one entity adopted or employed a technology after another entity had already used it.
-
D.
usedByTechnique
Indicates that a particular technique makes use of or employs the referenced entity as part of its method or process.
-
E.
laterFeature
Indicates that one feature, event, or element occurs or is introduced after another in time.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbb9bd5881909d86c5def7770fdd |
completed | April 20, 2026, 10:11 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:29 p.m.