Triple
T3956197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gipsy Danger chain sword |
E84983
|
entity |
| Predicate | franchiseElement |
P53123
|
FINISHED |
| Object | Jaeger weapon system |
—
|
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: Jaeger weapon system | Statement: [Gipsy Danger chain sword, franchiseElement, Jaeger weapon system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: franchiseElement Context triple: [Gipsy Danger chain sword, franchiseElement, Jaeger weapon system]
-
A.
franchiseOf
Indicates that one entity operates as a franchise belonging to or licensed by another entity.
-
B.
franchiseName
Indicates that an entity is identified by or associated with a specific franchise’s official name.
-
C.
basisOfFranchise
Indicates that one work or property serves as the foundational source or origin for a broader franchise or series.
-
D.
featuresFranchise
Indicates that one entity includes or presents a particular franchise as part of its content, offering, or composition.
-
E.
franchiseIconOf
Indicates that one entity serves as the primary symbolic character, logo, or emblem representing a particular franchise.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69aefaa3c6a08190bfe76629c7c98eea |
completed | March 9, 2026, 4:51 p.m. |
Created at: March 9, 2026, 3:30 p.m.