Triple
T15438073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perthes-lès-Hurlus |
E369820
|
entity |
| Predicate | frontLinePeriod |
P35162
|
FINISHED |
| Object | 1914–1915 |
—
|
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–1915 | Statement: [Perthes-lès-Hurlus, frontLinePeriod, 1914–1915]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontLinePeriod Context triple: [Perthes-lès-Hurlus, frontLinePeriod, 1914–1915]
-
A.
frontLineDuring
Indicates that an entity is positioned at or serves on the front line during a specified time or event.
-
B.
mainFrontlinePeriod
chosen
Indicates the time span during which an entity served as the primary or most active presence on the frontline.
-
C.
frontLine
Indicates that an entity is positioned at or associated with the foremost or primary line of engagement, activity, or defense relative to others.
-
D.
frontLineBetween
Indicates that a boundary or line of direct confrontation exists separating two opposing sides or regions.
-
E.
frontLineChange
Indicates a change in the position or configuration of the primary boundary or leading edge between opposing sides.
- 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03edca064819081510bf303271062 |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded28276f481908c2038bb301e57cf |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:21 a.m.