Triple
T18006622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Governor’s House, Calton Hill |
E430764
|
entity |
| Predicate | useCurrent |
P2156
|
FINISHED |
| Object | office accommodation |
—
|
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: office accommodation | Statement: [Governor’s House, Calton Hill, useCurrent, office accommodation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: useCurrent Context triple: [Governor’s House, Calton Hill, useCurrent, office accommodation]
-
A.
isCurrent
Indicates that something is presently valid, active, or up to date at the current point in time.
-
B.
associatedCurrent
Indicates a relationship where a particular current is linked or connected to another entity as its relevant or corresponding current.
-
C.
usedVia
Indicates that an entity performs or achieves something by means of, or through the use of, another entity or mechanism.
-
D.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
E.
actualUse
chosen
Indicates that an entity is currently being used or utilized in practice, as opposed to being merely available, planned, or potential.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b51c7da48190ab70775a672e2d5f |
completed | April 19, 2026, 10:57 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:24 a.m.