Triple
T20176328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Derwent church tower |
E492109
|
entity |
| Predicate | occasionallyVisible |
P47451
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Derwent church tower, occasionallyVisible, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occasionallyVisible Context triple: [Derwent church tower, occasionallyVisible, true]
-
A.
visibleAt
Indicates that one entity can be seen or perceived from a specific location, viewpoint, or context at a given time.
-
B.
occasionalRange
chosen
Indicates that the relationship or action occurs intermittently or at irregular intervals within a specified range or context.
-
C.
visibleUnder
Indicates that one entity can be seen or perceived when another specified condition, context, or covering entity is present or in effect.
-
D.
notVisibleWhen
Indicates that one entity is not visible whenever a specified condition, state, or context involving another entity holds.
-
E.
typicalVisibility
Indicates the usual or expected degree to which one entity can be seen or perceived from another under normal conditions.
- 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e668eb50a48190af7de53680ca2f5d |
completed | April 20, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:36 p.m.