Triple
T28144078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of the Forbidden Eye |
E714426
|
entity |
| Predicate | firstOpenedWithAttraction |
P200899
|
FINISHED |
| Object | 1995 |
—
|
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: 1995 | Statement: [Temple of the Forbidden Eye, firstOpenedWithAttraction, 1995]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstOpenedWithAttraction Context triple: [Temple of the Forbidden Eye, firstOpenedWithAttraction, 1995]
-
A.
openedWithAttraction
Indicates that something was initiated or begun due to a sense of attraction between the involved entities.
-
B.
openedAttraction
Indicates that an entity initiated the operation or public availability of an attraction at a specific time or event.
-
C.
introducedInAttraction
Indicates that an entity was first introduced or made its debut within a particular attraction.
-
D.
firstAppearanceInAttraction
Indicates that an entity makes its debut or is first introduced within a specific attraction.
-
E.
openingDayAttractionOf
Indicates that one entity serves as the main or featured attraction for another entity specifically on its opening day.
- 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_69efd6b033208190bf74f80a147e2092 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69ffb82be8148190a1c870d467a28c80 |
completed | May 9, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69ffb7bbd550819094052e9a0d0ae320 |
completed | May 9, 2026, 10:39 p.m. |
| PDg | Predicate description generation | batch_69ffb82b40788190bf401344a3f288dd |
completed | May 9, 2026, 10:41 p.m. |
Created at: April 27, 2026, 9:55 p.m.