Triple
T25510437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clan Ramsay |
E639360
|
entity |
| Predicate | hadMemberAtBattle |
P23441
|
FINISHED |
| Object | Battle of Bannockburn |
—
|
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: Battle of Bannockburn | Statement: [Clan Ramsay, hadMemberAtBattle, Battle of Bannockburn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadMemberAtBattle Context triple: [Clan Ramsay, hadMemberAtBattle, Battle of Bannockburn]
-
A.
battleParticipated
Indicates that an entity took part in a specific battle as a combatant or participant.
-
B.
battledIn
Indicates that two or more entities engaged in a battle or conflict that took place at a specific location or during a particular event.
-
C.
foughtAs
Indicates that an entity participated in a conflict or war in the capacity, role, or identity specified by another entity.
-
D.
associatedWithBattle
chosen
Indicates a relationship where an entity is connected or linked to a specific battle, such as by participation, relevance, or involvement.
-
E.
hadMember
Indicates that an entity was formerly a member or part of another entity or group.
- 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_69e75dbd09308190b6b5f0afdc12ec6d |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f809726081908ae4122cd4e581c1 |
completed | May 2, 2026, 1:11 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 2:48 p.m.