Triple
T7181927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gelsenkirchen |
E167466
|
entity |
| Predicate | wasFirstMentioned |
P4114
|
FINISHED |
| Object | 1150s |
—
|
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: 1150s | Statement: [Gelsenkirchen, wasFirstMentioned, 1150s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFirstMentioned Context triple: [Gelsenkirchen, wasFirstMentioned, 1150s]
-
A.
wasFirst
Indicates that one entity occurred, appeared, or held a position before another in time or sequence.
-
B.
eraMentioned
Indicates that a specific historical or temporal era is explicitly referenced or mentioned in a given context.
-
C.
firstMentionedInSeries
Indicates the work, episode, or installment in a series where a given entity is introduced or appears for the first time.
-
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_69c6888a7c548190a3d39b52a393080f |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e9b045c48190b27b2d6f7c11026f |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e74fb0f48190b2ad4dd4efdd241a |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:49 p.m.