Triple
T11849539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magnetic Hill |
E281871
|
entity |
| Predicate | hasOpticalIllusionType |
P101847
|
FINISHED |
| Object | gravity hill illusion |
—
|
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: gravity hill illusion | Statement: [Magnetic Hill, hasOpticalIllusionType, gravity hill illusion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpticalIllusionType Context triple: [Magnetic Hill, hasOpticalIllusionType, gravity hill illusion]
-
A.
hasStageIllusion
Indicates that one entity performs, features, or is associated with a particular stage illusion in a performance context.
-
B.
usesOpticsType
Indicates that one entity employs or is characterized by a specific type of optical system or technology.
-
C.
hasAberrationCharacteristics
Indicates that an entity exhibits traits or properties that deviate from what is considered normal, standard, or expected.
-
D.
hasRevelationType
Indicates the specific kind or category of revelation associated with an entity or event.
-
E.
blindedBy
Indicates that one entity causes another to lose the ability to see or perceive clearly, either literally or metaphorically.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a65db52c8190a218736da17d0153 |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a2573dbc8190ab432e8e28fde6cc |
completed | April 10, 2026, 7:10 a.m. |
| PDg | Predicate description generation | batch_69d8a43cc0c881909fed7cd759fe90b1 |
completed | April 10, 2026, 7:18 a.m. |
Created at: April 8, 2026, 9:43 p.m.