Triple
T11200486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breeds Hill |
E265025
|
entity |
| Predicate | battleNameOrigin |
P54889
|
FINISHED |
| Object | Battle of Bunker Hill named for nearby Bunker Hill |
—
|
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: Battle of Bunker Hill named for nearby Bunker Hill | Statement: [Breeds Hill, battleNameOrigin, Battle of Bunker Hill named for nearby Bunker Hill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleNameOrigin Context triple: [Breeds Hill, battleNameOrigin, Battle of Bunker Hill named for nearby Bunker Hill]
-
A.
historicalOriginMeaning
chosen
Indicates that one entity explains the original historical source or derivational meaning of another entity.
-
B.
clanNameOrigin
Indicates the source or basis from which a clan’s name is derived.
-
C.
battleAlsoKnownAs
Indicates that a particular battle is known by an alternative name or names.
-
D.
reasonForEpithet
Indicates the cause, motivation, or circumstance that explains why a particular epithet is applied to an entity.
-
E.
nomDeGuerre
Indicates that an entity uses or is known by a pseudonymous or war-related alias instead of their real name.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8c1e9f88190b2b42326aba9d778 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf83464819087529d47d025d313 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:29 p.m.