Triple
T4468807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finnish Whites |
E98443
|
entity |
| Predicate | conflictStartDate |
P44953
|
FINISHED |
| Object | 1918-01-27 |
—
|
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: 1918-01-27 | Statement: [Finnish Whites, conflictStartDate, 1918-01-27]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictStartDate Context triple: [Finnish Whites, conflictStartDate, 1918-01-27]
-
A.
conflictStartTime
Indicates the specific point in time at which a conflict between entities begins.
-
B.
conflictBeganInYear
chosen
Indicates that the specified conflict started or first broke out in the given calendar year.
-
C.
conflictPeriod
Indicates the time span during which a particular conflict or dispute is occurring or in effect between the related entities.
-
D.
conflictEndYear
Indicates the calendar year in which a particular conflict, dispute, or war came to an end.
-
E.
majorConflictYear
Indicates the year in which a major conflict, such as a war or large-scale violent confrontation, took place or reached a defining point.
- 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_69b3454b4ae481908967426dd37284d6 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b356fb69a0819099f0005779f4fcac |
completed | March 13, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69b3563bf4f8819081726cde3a34460b |
completed | March 13, 2026, 12:11 a.m. |
Created at: March 12, 2026, 11:34 p.m.