Triple
T37457449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dagger Mastery |
E930834
|
entity |
| Predicate | classSpecific |
P189036
|
FINISHED |
| Object | True |
—
|
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: True | Statement: [Dagger Mastery, classSpecific, True]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classSpecific Context triple: [Dagger Mastery, classSpecific, True]
-
A.
isClassSpecific
chosen
Indicates that something is restricted or uniquely applicable to a particular class or category, rather than being general or shared.
-
B.
exportSpecialization
Indicates a relationship where one entity specializes in exporting particular goods, services, or resources to another entity or market.
-
C.
clase
Indicates a classification or type relationship, where one entity is categorized as belonging to a particular class or category defined by another entity.
-
D.
branchSpecific
Indicates that something is associated with, restricted to, or applicable only within a particular branch or subdivision of a larger organization or structure.
-
E.
vendorSpecific
Indicates that something is defined, implemented, or applicable only for a particular vendor, rather than being generic or standardized.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:17 p.m.