Triple
T30803698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austrian government of Engelbert Dollfuss |
E784439
|
entity |
| Predicate | civilWarDate |
P134099
|
FINISHED |
| Object | February 1934 |
—
|
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: February 1934 | Statement: [Austrian government of Engelbert Dollfuss, civilWarDate, February 1934]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: civilWarDate Context triple: [Austrian government of Engelbert Dollfuss, civilWarDate, February 1934]
-
A.
civilWarStart
Indicates the point in time or event at which an internal armed conflict between factions of the same state or society begins.
-
B.
civilWarPeriod
Indicates a time span during which a civil war is occurring or in effect.
-
C.
civilWarEnd
Indicates that an internal armed conflict within a country has come to an official or de facto conclusion.
-
D.
dateOfConflict
chosen
Indicates the specific date or time period when a particular conflict, battle, or hostilities took place.
-
E.
hasCivilWarAssociation
Indicates a relationship in which an entity is connected or related to a civil war, such as through involvement, impact, or relevance.
- 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6903d362081909535bb042ea5f111 |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:42 p.m.