Triple
T3554151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Hobkirk’s Hill |
E75178
|
entity |
| Predicate | Rawdon’sObjective |
P24308
|
FINISHED |
| Object | to attack and disperse Greene’s army |
—
|
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: to attack and disperse Greene’s army | Statement: [Battle of Hobkirk’s Hill, Rawdon’sObjective, to attack and disperse Greene’s army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Rawdon’sObjective Context triple: [Battle of Hobkirk’s Hill, Rawdon’sObjective, to attack and disperse Greene’s army]
-
A.
expeditionObjective
chosen
Indicates the primary goal or purpose that an expedition is intended to achieve.
-
B.
EVAobjective
Indicates that an extravehicular activity (EVA) is performed with the purpose of achieving a specific objective or goal.
-
C.
intendedMission
Indicates that one entity is the planned or designated mission, task, or objective associated with another entity.
-
D.
finalMissionOf
Indicates that one entity is the last mission, assignment, or operation undertaken by another entity.
-
E.
laterGoal
Indicates that one goal occurs or is intended to be achieved after another goal in time.
- 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_69ad85d33c6c819081d5ac1df13b5680 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc05549d88190acdebdd542ea1a67 |
completed | March 8, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69adb83270ac819083967db0570167d2 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:20 p.m.