Triple
T3954175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yeomen of the Guard |
E84936
|
entity |
| Predicate | ceremonialWeapon |
P7745
|
FINISHED |
| Object | partisan |
—
|
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: partisan | Statement: [Yeomen of the Guard, ceremonialWeapon, partisan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceremonialWeapon Context triple: [Yeomen of the Guard, ceremonialWeapon, partisan]
-
A.
ceremonialUse
Indicates that something is used in a ritual, religious, or formal ceremony rather than for ordinary or practical purposes.
-
B.
typicalWeapon
chosen
Indicates that the object is a weapon commonly or characteristically used by the subject.
-
C.
armedBy
Indicates that one entity is supplied with weapons, equipment, or armaments by another entity.
-
D.
usedWeapon
Indicates that an entity employed a specific weapon as the means or tool to carry out an action or event.
-
E.
weapon
Indicates that one entity is used as a weapon by, or serves as the weapon of, another entity.
- 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_69aed934fbfc8190847068e4546de963 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaa5afdc8190b709af2473d75d02 |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8ed04e4819096bced8971cd888d |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:30 p.m.