Triple
T16211471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haunted Castle |
E393475
|
entity |
| Predicate | hasPrimaryExperience |
P22360
|
FINISHED |
| Object | 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: visual effects | Statement: [Haunted Castle, hasPrimaryExperience, visual effects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryExperience Context triple: [Haunted Castle, hasPrimaryExperience, visual effects]
-
A.
hasExperienceElement
Indicates that an experience is composed of, or includes, a specific constituent element or component.
-
B.
primaryExperience
chosen
Indicates that one entity is the main or most significant experience associated with another entity, as opposed to secondary or supporting experiences.
-
C.
hasGlobalExperience
Indicates that an entity possesses experience gained from working, operating, or engaging across multiple countries or international contexts.
-
D.
typeOfExperience
Indicates that one entity specifies the category or nature of an experience associated with another entity.
-
E.
hasWorkedIn
Indicates that a person has been employed or has performed work within a particular organization, location, or domain for some period of 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e227f1bef8819094e724f5cd0b86d5 |
completed | April 17, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.