Triple
T34052934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reynolds’ Battle |
E873272
|
entity |
| Predicate | USCommanderFullName |
P10574
|
FINISHED |
| Object | Joseph Jones Reynolds |
—
|
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: Joseph Jones Reynolds | Statement: [Reynolds’ Battle, USCommanderFullName, Joseph Jones Reynolds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: USCommanderFullName Context triple: [Reynolds’ Battle, USCommanderFullName, Joseph Jones Reynolds]
-
A.
commanderFullName
chosen
Indicates that the predicate specifies the complete personal name of the commander associated with an entity.
-
B.
RepublicanCommander
Indicates that an individual serves as a military commander for the Republican side in a conflict.
-
C.
commanderAlsoServesAs
Indicates that the person who holds a commander role simultaneously fulfills one or more additional official roles or positions.
-
D.
UnionCommanderOfAssault
Indicates that the subject served as the commanding Union officer in charge of a specific military assault.
-
E.
commanderUnitedStates
Indicates that one entity serves as the commander of a United States military or governmental unit, mission, or operation.
- 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_69f349a3ec2c8190b62da76e54231a0f |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:52 a.m.