Triple
T38369965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HarmonQuest |
E892549
|
entity |
| Predicate | usesSystemSimilarTo |
P70832
|
FINISHED |
| Object | Dungeons & Dragons |
—
|
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: Dungeons & Dragons | Statement: [HarmonQuest, usesSystemSimilarTo, Dungeons & Dragons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSystemSimilarTo Context triple: [HarmonQuest, usesSystemSimilarTo, Dungeons & Dragons]
-
A.
usesSameSystemAs
chosen
Indicates that two entities operate within or rely on the same underlying system, platform, or infrastructure.
-
B.
hasSimilarityTo
Indicates that one entity shares common characteristics, features, or qualities with another entity to a notable degree.
-
C.
lessSimilarTo
Indicates that one entity is considered to share fewer similarities or a weaker resemblance with another entity compared to some reference or alternative.
-
D.
inSameSystemAs
Indicates that two entities are located within or belong to the same overarching system or framework.
-
E.
userInterfaceSimilarTo
Indicates that one user interface resembles or closely matches another in appearance, layout, or interaction style.
- 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_69f76e47cb4c8190bdd92cd1db59c0c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: May 3, 2026, 4:31 p.m.