Triple
T21526336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Henry campaign |
E531105
|
entity |
| Predicate | riverineWarfare |
P82065
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Fort Henry campaign, riverineWarfare, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverineWarfare Context triple: [Fort Henry campaign, riverineWarfare, true]
-
A.
navalOperations
Indicates involvement in planning, conducting, or supporting military activities carried out by naval forces at sea or from the sea.
-
B.
mediumOfWarWith
chosen
Indicates a relationship where a particular medium (such as a tool, method, or channel) is used to conduct, facilitate, or engage in war or armed conflict with another party.
-
C.
riverCrossedByAllies
Indicates that the river was traversed or crossed by allied forces.
-
D.
riverinePeople
Indicates a relationship where people live along, depend on, or are closely associated with rivers and river environments.
-
E.
sinkingConflict
Indicates a situation where one entity’s decline, failure, or deterioration creates or intensifies a conflict with another entity.
- 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_69e0c45d95a081908e7962ad215da746 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee88515874819085e251c0d297a587 |
completed | April 26, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:26 p.m.