Triple
T28290209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saarland industrial region |
E713401
|
entity |
| Predicate | importantPeriod |
P16254
|
FINISHED |
| Object | First World War era |
—
|
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: First World War era | Statement: [Saarland industrial region, importantPeriod, First World War era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importantPeriod Context triple: [Saarland industrial region, importantPeriod, First World War era]
-
A.
timePeriodOfMajorImportance
chosen
Indicates that a particular time period holds significant importance or prominence within a given context or domain.
-
B.
notablePeriodOfInterest
Indicates a time span that is particularly significant or noteworthy in relation to the subject.
-
C.
focusPeriod
Indicates the specific time span during which attention, activity, or analysis is concentrated on something.
-
D.
importantNote
Indicates that one entity is marked as an important or noteworthy note in relation to another entity.
-
E.
importantObject
Indicates that one entity is considered especially significant, central, or of high priority in relation to another entity or context.
- 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_69efb52371d88190a1381c4e58a3b731 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 27, 2026, 11:29 p.m.