Triple
T30872572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florida frontier |
E786381
|
entity |
| Predicate | mainConflictParty |
P167916
|
FINISHED |
| Object | United States Army |
—
|
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: United States Army | Statement: [Florida frontier, mainConflictParty, United States Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainConflictParty Context triple: [Florida frontier, mainConflictParty, United States Army]
-
A.
mainConflict
Indicates the primary opposing force, problem, or struggle that drives tension and narrative progression between entities or sides.
-
B.
partnerInConflictWith
Indicates that two entities are engaged as opposing partners or sides within the same conflict or dispute.
-
C.
mainParties
Indicates the primary entities that are directly and centrally involved in a given relationship, event, or agreement.
-
D.
rivalParty
Indicates that one party is in competition or opposition with another party, often pursuing conflicting goals or interests.
-
E.
conflictParticipantIn
chosen
Indicates that an entity takes part as a participant in a specific conflict or dispute.
- 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_69f224b9df2c819086f55f8bcf7f382e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 29, 2026, 8:48 p.m.