Triple
T7956148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strathnaver |
E184742
|
entity |
| Predicate | clearancePeriod |
P80008
|
FINISHED |
| Object | early 19th century |
—
|
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: early 19th century | Statement: [Strathnaver, clearancePeriod, early 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clearancePeriod Context triple: [Strathnaver, clearancePeriod, early 19th century]
-
A.
removalPeriod
Indicates the time span during which something is taken away, deleted, or otherwise removed from availability or consideration.
-
B.
withdrawalGracePeriod
Indicates the time window after an action or event during which a withdrawal can be made without incurring penalties or additional restrictions.
-
C.
settlementPeriod
Indicates the length of time between a transaction or agreement and its final settlement or completion.
-
D.
rescissionPeriod
Indicates the time span during which a party is allowed to cancel or revoke an agreement or transaction without penalty.
-
E.
refusalPeriodMaximum
Indicates the maximum allowed duration within which a refusal can occur or remain valid in the context of the related relationship or action.
- F. None of above. chosen
Provenance (4 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_69ca8292cba881908a64427b938dac47 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b7d36c081908cc8760a0dbf6001 |
completed | March 31, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69cb0473d7dc8190a25d0cf460b9fcbe |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bbbacc81909c6cf8ec35314bbb |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:11 p.m.