Triple
T31762646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meuse region |
E810721
|
entity |
| Predicate | timePeriodOfPeakSignificance |
P16254
|
FINISHED |
| Object | 1914–1918 |
—
|
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: 1914–1918 | Statement: [Meuse region, timePeriodOfPeakSignificance, 1914–1918]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfPeakSignificance Context triple: [Meuse region, timePeriodOfPeakSignificance, 1914–1918]
-
A.
timePeriodOfMajorImportance
chosen
Indicates that a particular time period holds significant importance or prominence within a given context or domain.
-
B.
timeSignificance
Indicates the degree to which a specific point or interval in time is important, impactful, or meaningful within a given context.
-
C.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
D.
timePeriodFormulated
Indicates the time period during which something (such as a concept, theory, or plan) was formulated or developed.
-
E.
timePeriodInfluence
Indicates that one time period has an influence or shaping effect on another time period or on events occurring within it.
- 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_69f348e463e08190b902d4819195e1f0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 30, 2026, 11:31 p.m.