Triple
T38548809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schemnitz |
E925047
|
entity |
| Predicate | historicallyUsedUntil |
P6544
|
FINISHED |
| Object | 20th 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: 20th century | Statement: [Schemnitz, historicallyUsedUntil, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyUsedUntil Context triple: [Schemnitz, historicallyUsedUntil, 20th century]
-
A.
historicallyUsedFor
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
-
B.
existedUntil
Indicates that an entity continued to exist up to, but not necessarily beyond, a specified time or event.
-
C.
usedToDate
Indicates that two entities were previously in a romantic or dating relationship but are no longer together.
-
D.
usedUntil
chosen
Indicates that something remained in use or operation up to a specified time or event, after which it was no longer used.
-
E.
historicalPeriodOfUse
Indicates the time period during which something was in active use or commonly utilized.
- 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_69f76eaeb69c8190b367df9330d6f6af |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a02f441bd408190923b6b68adee8fde |
completed | May 12, 2026, 9:34 a.m. |
| PD | Predicate disambiguation | batch_6a02f3c1e64881908569423c9f298f26 |
completed | May 12, 2026, 9:32 a.m. |
Created at: May 3, 2026, 4:32 p.m.