Triple
T2841191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philip (King Philip) |
E62470
|
entity |
| Predicate | startTimeOfMajorConflict |
P40469
|
FINISHED |
| Object | 1675 |
—
|
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: 1675 | Statement: [Philip (King Philip), startTimeOfMajorConflict, 1675]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeOfMajorConflict Context triple: [Philip (King Philip), startTimeOfMajorConflict, 1675]
-
A.
lastWarStart
Indicates the point in time when the most recent war involving the given entity or entities began.
-
B.
majorConflictYear
chosen
Indicates the year in which a major conflict, such as a war or large-scale violent confrontation, took place or reached a defining point.
-
C.
chronologyWithinConflict
Indicates that one event or time period occurs within the temporal span of a specified conflict or war.
-
D.
beganDuringConflict
Indicates that the action or relationship started while a specified conflict was ongoing.
-
E.
conflictEndYear
Indicates the calendar year in which a particular conflict, dispute, or war came to an end.
- 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_69ab4c3d16bc81908b3a1c98fbd287fe |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf16d0c08190bb8de4a4160b4414 |
completed | March 7, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69abdd0ce8b08190ba28c192988f38ce |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:01 p.m.