Triple
T27904020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | III Corps (Union Army) |
E705718
|
entity |
| Predicate | engagedLocation |
P164363
|
FINISHED |
| Object | Peach Orchard |
—
|
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: Peach Orchard | Statement: [III Corps (Union Army), engagedLocation, Peach Orchard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engagedLocation Context triple: [III Corps (Union Army), engagedLocation, Peach Orchard]
-
A.
agingLocation
Indicates the place where an entity undergoes an aging process or is stored to age over time.
-
B.
plannedLocation
Indicates the intended or scheduled location where an entity is expected to be or an event is planned to occur.
-
C.
hasLocationRole
Indicates that an entity holds or plays a specific role in relation to a particular location (e.g., origin, destination, storage site, or operational area).
-
D.
assignedLocation
Indicates that a specific location has been designated or allocated to an entity as its place for presence, use, or operation.
-
E.
connectsLocation
Indicates a relationship where one entity serves as a link or route that joins or provides access between two locations.
- 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_69ef96b5aad08190be36a277c31e7004 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f644de4a84819087ddb84757fc4585 |
completed | May 2, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f643e818d481908fc66bc91bd25d77 |
completed | May 2, 2026, 6:35 p.m. |
Created at: April 27, 2026, 6:44 p.m.