Triple

T3029179

Position	Surface form	Disambiguated ID	Type / Status
Subject	Overland Campaign	`E82848`	entity
Predicate	leeRole	`P268`	FINISHED
Object	defensive commander attempting to protect Richmond and his army	`—`	LITERAL GENERATED

How this triple was built (1 step)

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.

PD Predicate disambiguation gpt-5-mini-2025-08-07

Target predicate: leeRole
Context triple: [Overland Campaign, leeRole, defensive commander attempting to protect Richmond and his army]

A. unitRole
Indicates the functional role or purpose that a unit serves within a larger system or context.
B. deFactoRole
Indicates that an entity effectively functions in a role or capacity in practice, even if that role is not formally or officially assigned.
C. role chosen
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
D. possibleRole
Indicates that an entity is capable of or eligible to serve in a particular role or function in a given context.
E. roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
F. None of above.

Provenance (2 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_69ad8b21a62881908ec5dd4fba4a187c`	completed	March 8, 2026, 2:43 p.m.
PD	Predicate disambiguation	`batch_69ad961e2a408190afb1759132701305`	completed	March 8, 2026, 3:30 p.m.

Created at: March 8, 2026, 3 p.m.