Triple
T11849575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magnetic Hill |
E281871
|
entity |
| Predicate | hasVisitorBehavior |
P85061
|
FINISHED |
| Object | visitors record videos of the 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: visitors record videos of the illusion | Statement: [Magnetic Hill, hasVisitorBehavior, visitors record videos of the illusion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVisitorBehavior Context triple: [Magnetic Hill, hasVisitorBehavior, visitors record videos of the illusion]
-
A.
hasVisitorType
Indicates the type or category of visitor associated with an entity (e.g., guest, customer, tourist, patient).
-
B.
hasVisitorCharacteristic
chosen
Indicates that a visitor possesses or exhibits a particular characteristic, attribute, or quality.
-
C.
hasVisitorBuilding
Indicates that a particular building serves as a designated visitor facility or is intended for use by visitors.
-
D.
hasVisitation
Indicates that one entity visits, or is allowed or scheduled to visit, another entity or location.
-
E.
hasVisitorPolicy
Indicates that an entity has an established policy governing the presence, behavior, or permissions of visitors.
- 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_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. |
Created at: April 8, 2026, 9:43 p.m.