Triple
T36237859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Hill |
E891421
|
entity |
| Predicate | divisionCommanded |
P19105
|
FINISHED |
| Object | 52nd (Lowland) Infantry Division |
E257072
|
NE 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: 52nd (Lowland) Infantry Division | Statement: [John Hill, divisionCommanded, 52nd (Lowland) Infantry Division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divisionCommanded Context triple: [John Hill, divisionCommanded, 52nd (Lowland) Infantry Division]
-
A.
divisionOfCommand
Indicates a hierarchical relationship where one entity holds authority or command over another within an organizational or military structure.
-
B.
commandedIn
Indicates that one entity held a position of command or leadership within a specified context, such as a battle, operation, or organization.
-
C.
commandOf
chosen
Indicates that one entity holds authoritative control or leadership over another, typically in a military, organizational, or hierarchical context.
-
D.
commandedTo
Indicates that one entity has issued an order or directive for another entity to perform a specific action or fulfill a particular duty.
-
E.
divisionRenamedFrom
Indicates that a division currently known by one name was previously known by another specified name.
- F. None of above.
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_69f76e44993481908fa75e4c48d0aab3 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a397d71ff7c8190a707acdd42813578 |
completed | June 22, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:09 p.m.