Triple
T24809734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Seal of Scotland |
E620750
|
entity |
| Predicate | continuesInUseAfter |
P109522
|
FINISHED |
| Object | Acts of Union 1707 |
—
|
NE NERFINISHED |
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: Acts of Union 1707 | Statement: [Great Seal of Scotland, continuesInUseAfter, Acts of Union 1707]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuesInUseAfter Context triple: [Great Seal of Scotland, continuesInUseAfter, Acts of Union 1707]
-
A.
continuouslyUsedAs
Indicates that one entity is persistently and repeatedly employed or utilized as another entity or for a particular function over an extended, uninterrupted period.
-
B.
stillUsedBy
Indicates that something continues to be used or relied upon by another entity at the present time.
-
C.
continuesFor
Indicates that an event, state, or process persists or remains in effect for a specified duration or period.
-
D.
subsequentUse
Indicates that one entity is used, applied, or consumed after another entity in time or sequence.
-
E.
continuedRelevanceAfterEndDate
chosen
Indicates that something remains relevant or applicable even after its specified end date has passed.
- 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 18, 2026, 4:50 a.m.