Triple
T14903238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roxburgh, Scotland |
E360060
|
entity |
| Predicate | timePeriodOfGreatestImportance |
P16254
|
FINISHED |
| Object | 12th 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: 12th century | Statement: [Roxburgh, Scotland, timePeriodOfGreatestImportance, 12th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfGreatestImportance Context triple: [Roxburgh, Scotland, timePeriodOfGreatestImportance, 12th century]
-
A.
timePeriodOfMajorImportance
chosen
Indicates that a particular time period holds significant importance or prominence within a given context or domain.
-
B.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
C.
timePeriodCategory
Indicates the classification of a time period into a specific category or type (e.g., era, phase, or temporal grouping).
-
D.
focusPeriod
Indicates the specific time span during which attention, activity, or analysis is concentrated on something.
-
E.
screenTimeImportance
Indicates how important or significant the amount of time spent using screens or digital devices is considered in a given context.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded60b24008190bd272c0d61329400 |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a4a14a88190951bb8f4c60bd37b |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:11 a.m.