Triple
T6186023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schwerin |
E138060
|
entity |
| Predicate | historicalFirstMention |
P3921
|
FINISHED |
| Object | 11th 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: 11th century | Statement: [Schwerin, historicalFirstMention, 11th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalFirstMention Context triple: [Schwerin, historicalFirstMention, 11th century]
-
A.
firstHistoricalUse
Indicates that the subject entity represents the earliest known or recorded instance of the object entity being used or occurring in history.
-
B.
historicalPeriodOfFirstUse
Indicates the historical time period during which something was first used or came into use.
-
C.
firstClearlyAttestedIn
chosen
Indicates the earliest known point in time or source where something is clearly documented or evidenced.
-
D.
firstCelebratedInYear
Indicates the year in which something (such as an event, holiday, or celebration) was first observed or celebrated.
-
E.
firstAppearedAt
Indicates the point in time or specific event at which an entity was first introduced, observed, or became known.
- 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_69c008a8fd408190b7ec6e42934974a6 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062150fc48190877240abe6b6c636 |
completed | March 22, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69c055fa0a808190bda37832e3ac150c |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:19 p.m.