Triple
T37811852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earldom of Mar |
E942666
|
entity |
| Predicate | traditionalCreationPeriod |
P44840
|
FINISHED |
| Object | early Middle Ages |
—
|
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 Middle Ages | Statement: [Earldom of Mar, traditionalCreationPeriod, early Middle Ages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalCreationPeriod Context triple: [Earldom of Mar, traditionalCreationPeriod, early Middle Ages]
-
A.
timeSpanOfCreation
Indicates the period of time during which the creation of an entity took place.
-
B.
titleCreationPeriod
chosen
Indicates the time span or historical period during which a title was originally created or established.
-
C.
effectiveCreationDate
Indicates the date on which something actually comes into effect or becomes valid, as opposed to when it was merely created or recorded.
-
D.
establishedPeriod
Indicates the time span or date range during which something was founded, created, or formally brought into existence.
-
E.
foundingPeriod
Indicates the time span or historical period during which an entity (such as an organization, settlement, or institution) was founded.
- 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_69f76ee8104c8190ab17133ccd8f86e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffdf47d9608190830ca23d9cef6409 |
completed | May 10, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69ffdf00e2b4819082dd5cb78f316baf |
completed | May 10, 2026, 1:27 a.m. |
Created at: May 3, 2026, 4:19 p.m.