Triple
T7799616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bautzen |
E180394
|
entity |
| Predicate | wasFirstMentionedIn |
P4114
|
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: [Bautzen, wasFirstMentionedIn, 11th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFirstMentionedIn Context triple: [Bautzen, wasFirstMentionedIn, 11th century]
-
A.
wasFirst
Indicates that one entity occurred, appeared, or held a position before another in time or sequence.
-
B.
firstMentionedInSeries
Indicates the work, episode, or installment in a series where a given entity is introduced or appears for the first time.
-
C.
eraMentioned
Indicates that a specific historical or temporal era is explicitly referenced or mentioned in a given context.
-
D.
firstAppeared
chosen
Indicates the earliest known time or context in which an entity was introduced, observed, or came into existence.
-
E.
mentionedAs
Indicates that one entity is referred to or cited by name or description in the context of another entity.
- 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_69ca827e50cc8190a92a733577184938 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78a6d88819093f83528fe88b182 |
completed | March 30, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cae9111b2481909684a2d4aa4831c2 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:32 p.m.