Triple
T149260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acts of Parliament |
E3395
|
entity |
| Predicate | historicallyRecordedSince |
P6054
|
FINISHED |
| Object | medieval period |
—
|
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: medieval period | Statement: [Acts of Parliament, historicallyRecordedSince, medieval period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyRecordedSince Context triple: [Acts of Parliament, historicallyRecordedSince, medieval period]
-
A.
isHistoric
Indicates that something has significant importance or relevance in history, often due to its age, impact, or role in past events.
-
B.
historicalRecordStatus
Indicates the status or condition of a record within a historical or archival context (e.g., active, archived, revised, or obsolete).
-
C.
hasLongTermDatasetSince
Indicates that an entity has maintained or used a particular dataset continuously starting from a specified point in time.
-
D.
historicallyBorneBy
Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
-
E.
historicalPeriodOfUse
Indicates the time period during which something was in active use or commonly utilized.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2580ca15481909fa3e87d804a1b23 |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a256599db08190a7b000b381d32ec4 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a25737f9188190b9690dce98aed83a |
completed | Feb. 28, 2026, 2:47 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.