Triple
T32097125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beater |
E819747
|
entity |
| Predicate | isCompanionWeaponOf |
P22238
|
FINISHED |
| Object | Orcrist |
—
|
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: Orcrist | Statement: [Beater, isCompanionWeaponOf, Orcrist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCompanionWeaponOf Context triple: [Beater, isCompanionWeaponOf, Orcrist]
-
A.
associatedWithWeapon
Indicates that an entity has a connection or involvement with a weapon, such as ownership, use, presence, or relevance in a given context.
-
B.
weaponForgedFor
Indicates that a weapon was specifically created or crafted for a particular entity, purpose, or context.
-
C.
oftenEquippedWith
Indicates that one type of entity is frequently or typically outfitted, furnished, or supplied with another entity.
-
D.
hasCompanionPiece
chosen
Indicates that one item is conceptually or functionally paired with another item as its companion piece.
-
E.
refersToWeaponSuccessor
Indicates that one weapon is recognized as the successor or follow-up version to another weapon.
- 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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 12:26 a.m.