Triple
T20696553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Haunting of Ghostly Greens |
E508674
|
entity |
| Predicate | experiencePace |
P141122
|
FINISHED |
| Object | self-guided |
—
|
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: self-guided | Statement: [The Haunting of Ghostly Greens, experiencePace, self-guided]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: experiencePace Context triple: [The Haunting of Ghostly Greens, experiencePace, self-guided]
-
A.
experienceType
Indicates the specific kind or category of experience associated with an entity or event.
-
B.
experienceDuration
Indicates the length of time over which an entity undergoes or has undergone a particular experience or event.
-
C.
experienceStyle
Indicates that one entity has or is associated with a particular manner, approach, or style in which an experience is delivered or undergone.
-
D.
settingOfExperience
Indicates that a particular context, environment, or situation serves as the backdrop or circumstances in which an experience occurs.
-
E.
experienceIncludes
Indicates that a particular experience encompasses, contains, or involves a specified component, activity, or element as part of it.
- 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_69e0b4c2b2a481909e31e9cb8f81ab55 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6c1123d7c81908a1d16923437266d |
completed | April 21, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3caef50819093c8159fe8d6435b |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:10 p.m.