Triple
T24978772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Stark |
E625100
|
entity |
| Predicate | priorConflict |
P4335
|
FINISHED |
| Object | French and Indian War |
—
|
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: French and Indian War | Statement: [John Stark, priorConflict, French and Indian War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: priorConflict Context triple: [John Stark, priorConflict, French and Indian War]
-
A.
previousConflict
chosen
Indicates that a conflict or dispute occurred between the entities at some earlier time prior to the current context.
-
B.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
C.
facedConflictOver
Indicates that two or more entities experienced opposition, dispute, or tension concerning a particular issue, resource, or situation.
-
D.
subsequentConflict
Indicates that one conflict occurs after and is temporally subsequent to another conflict.
-
E.
originatingConflict
Indicates the conflict or dispute from which another event, situation, or relationship initially arises or is caused.
- 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:02 a.m.