Triple
T21760592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Henry |
E537152
|
entity |
| Predicate | fallContributedTo |
P145251
|
FINISHED |
| Object | Union advance into Tennessee |
—
|
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: Union advance into Tennessee | Statement: [Fort Henry, fallContributedTo, Union advance into Tennessee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fallContributedTo Context triple: [Fort Henry, fallContributedTo, Union advance into Tennessee]
-
A.
fallStatus
Indicates the condition or outcome of a fall event affecting an entity.
-
B.
fellWith
Indicates that one entity fell at the same time as, or in conjunction with, another entity.
-
C.
fellOn
Indicates that one entity moved downward, typically due to gravity, and came to rest on the surface of another entity.
-
D.
fallCause
Indicates that one event or condition causes or brings about another event of falling or decline.
-
E.
fell
Indicates that an entity moved downward from a higher position to a lower one, typically due to gravity, often unintentionally or uncontrollably.
- F. None of above. chosen
Provenance (4 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_69e0c46f5d1c8190bf830409e98464e5 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01d91e9788190a11d0295306e78a4 |
completed | April 28, 2026, 2:38 a.m. |
| PD | Predicate disambiguation | batch_69e6969e46088190b13d6e9025775ea3 |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4c438c819089ab285e64e81d24 |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:50 p.m.