Triple
T35398679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ross Castle |
E1023156
|
entity |
| Predicate | garrisonCommanderAtSurrender |
P31312
|
FINISHED |
| Object | Lord Muskerry |
—
|
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: Lord Muskerry | Statement: [Ross Castle, garrisonCommanderAtSurrender, Lord Muskerry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: garrisonCommanderAtSurrender Context triple: [Ross Castle, garrisonCommanderAtSurrender, Lord Muskerry]
-
A.
garrisonSurrenderedTo
Indicates that a defending military garrison formally capitulated and yielded control to another party.
-
B.
surrenderedCommander
Indicates that one commander formally yielded authority or control to another, typically as part of a surrender.
-
C.
garrisonCommander
chosen
Indicates that one entity serves as the commanding officer in charge of the military garrison located at or associated with another entity.
-
D.
garrisonCommand
Indicates that one entity holds command authority over the garrison or stationed military forces at a particular location.
-
E.
garrisonDestroyed
Indicates that a military garrison has been eliminated or rendered nonfunctional, typically through attack or destruction.
- 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_69f76df43ca4819098711ca4370f1bb9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7953827b48190aec5b07f65a3b304 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.