Triple
T23197060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wiltshire section |
E579898
|
entity |
| Predicate | hasInteractionStyle |
P146301
|
FINISHED |
| Object | point-and-click exploration |
—
|
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: point-and-click exploration | Statement: [Wiltshire section, hasInteractionStyle, point-and-click exploration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInteractionStyle Context triple: [Wiltshire section, hasInteractionStyle, point-and-click exploration]
-
A.
hasInteractionMode
chosen
Indicates the way in which two entities engage or interact with each other, specifying the manner, channel, or pattern of their interaction.
-
B.
supportsUserInteraction
Indicates that an entity enables or facilitates direct interaction with a user, such as receiving input or providing responsive feedback.
-
C.
hasInteraction
Indicates that there is some form of interaction or mutual action occurring between the related entities.
-
D.
hasTouchControls
Indicates that an entity supports or is operated through touch-based input controls.
-
E.
hasStylus
Indicates that an entity possesses or is equipped with a stylus as an accessory or tool.
- 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_69e24600eed08190bd7e5295653a1503 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18fdc0b8081909242fdc5cb1da517 |
completed | April 29, 2026, 4:58 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:06 p.m.