Triple
T37459103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lightbomb |
E930872
|
entity |
| Predicate | canBeDiscoveredBy |
P113006
|
FINISHED |
| Object | Priest spell generation effects |
—
|
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: Priest spell generation effects | Statement: [Lightbomb, canBeDiscoveredBy, Priest spell generation effects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeDiscoveredBy Context triple: [Lightbomb, canBeDiscoveredBy, Priest spell generation effects]
-
A.
isDiscoveredBy
chosen
Indicates that something (such as an object, fact, or phenomenon) is found, identified, or revealed by a particular agent or entity.
-
B.
hasNearbyDiscovery
Indicates that one entity has a discovery located in close physical or spatial proximity to it.
-
C.
attributedDiscovery
Indicates that the discovery of something is credited or assigned to a particular agent or entity.
-
D.
hasDiscoveryFeature
Indicates that an entity includes or supports a capability for discovering, finding, or surfacing other relevant entities, items, or information.
-
E.
hasDiscoveryCatalog
Indicates that an entity is associated with a specific discovery catalog in which it is recorded or listed.
- 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_69ff1c91bbac8190b84012dee1cb3b2c |
completed | May 9, 2026, 11:37 a.m. |
| PD | Predicate disambiguation | batch_69ff1c23ca508190bb5a435d765b7e53 |
completed | May 9, 2026, 11:36 a.m. |
Created at: May 3, 2026, 4:17 p.m.