Triple
T25461978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schleswig Wars |
E638071
|
entity |
| Predicate | hasPartEndTime |
P118268
|
FINISHED |
| Object | First Schleswig War, 1851 |
—
|
NE NERFINISHED |
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 Schleswig War, 1851 | Statement: [Schleswig Wars, hasPartEndTime, First Schleswig War, 1851]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartEndTime Context triple: [Schleswig Wars, hasPartEndTime, First Schleswig War, 1851]
-
A.
hasPartStartTime
Indicates the time at which a specific part or segment of an entity, event, or process begins.
-
B.
hasTemporalEnd
chosen
Indicates that an event, state, or process concludes or terminates at a specific point or interval in time.
-
C.
hasCutoffTime
Indicates that there is a specific time limit or deadline by which an action, event, or process must be completed or initiated.
-
D.
hasDepartureEnd
Indicates that an entity marks the endpoint or final location of a departure event or journey.
-
E.
hasTimeStart
Indicates that an event, process, or state begins at a specific point in time.
- 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 21, 2026, 2:12 p.m.