Triple
T9384027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilderness (Virginia woodland) |
E225858
|
entity |
| Predicate | effectOnBattle |
P51648
|
FINISHED |
| Object | disorganized troop formations |
—
|
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: disorganized troop formations | Statement: [Wilderness (Virginia woodland), effectOnBattle, disorganized troop formations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnBattle Context triple: [Wilderness (Virginia woodland), effectOnBattle, disorganized troop formations]
-
A.
controlDuringBattle
Indicates that one entity exerts command, influence, or strategic direction over another specifically in the context of a battle or combat situation.
-
B.
functionDuringBattle
chosen
Indicates a functional role, effect, or behavior that specifically occurs or is active during a battle.
-
C.
usedInBattle
Indicates that something (typically a tool, strategy, or resource) was employed or applied during a battle or combat situation.
-
D.
featuresBattle
Indicates that one entity includes, presents, or involves a battle as a significant element or event.
-
E.
effectOnShips
Indicates the impact or influence that one entity, event, or condition has on ships.
- 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_69ca842e9dcc8190a264119e683cfe04 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd50c23e7881908112597a1771afa5 |
completed | April 1, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69cca53bd6ec81909bf403ce304e5c08 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:44 p.m.