Triple
T22735332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Claiborne |
E562253
|
entity |
| Predicate | hadConflict |
P4335
|
FINISHED |
| Object | armed clashes with Maryland forces in the 1630s |
—
|
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: armed clashes with Maryland forces in the 1630s | Statement: [William Claiborne, hadConflict, armed clashes with Maryland forces in the 1630s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadConflict Context triple: [William Claiborne, hadConflict, armed clashes with Maryland forces in the 1630s]
-
A.
endedConflict
Indicates that a previously ongoing conflict between entities has been brought to an end.
-
B.
previousConflict
chosen
Indicates that a conflict or dispute occurred between the entities at some earlier time prior to the current context.
-
C.
wonConflict
Indicates that one entity has prevailed over another in a conflict, contest, or struggle.
-
D.
reportedConflict
Indicates that one party has formally reported the existence of a conflict involving another party or situation.
-
E.
conflictedBetween
Indicates being torn or uncertain between two or more options, positions, or commitments.
- 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_69e24550859c81908727d91efc3a81b4 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1796f030881908e141564d442bd1b |
completed | April 29, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69eed2a971c0819088af574e40c9343f |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:22 p.m.