Triple
T3136838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parliament House, Edinburgh |
E65551
|
entity |
| Predicate | historicalUseEnd |
P14594
|
FINISHED |
| Object | 1707 |
—
|
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: 1707 | Statement: [Parliament House, Edinburgh, historicalUseEnd, 1707]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalUseEnd Context triple: [Parliament House, Edinburgh, historicalUseEnd, 1707]
-
A.
historicalPeriodOfUse
Indicates the time period during which something was in active use or commonly utilized.
-
B.
militaryUseEnd
chosen
Indicates the point in time or condition at which the military use of something (such as a facility, resource, or asset) ceases.
-
C.
historicallyUsedFor
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
-
D.
historicalUsageDeclinedAfter
Indicates that the frequency or prevalence of using something has decreased after a specified time, event, or condition.
-
E.
historicUsePersistsIn
Indicates that a practice, feature, or condition originating in the past continues to exist or be applied in the present.
- 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_69ad8581c25c8190b0d85ba9b9baa531 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada564eacc8190a54d07b4eb31c196 |
completed | March 8, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69ad9df840088190a26a1516f4c1f056 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.