Triple
T20194417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thunder Stone |
E493044
|
entity |
| Predicate | associatedType |
P43530
|
FINISHED |
| Object | Electric |
—
|
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: Electric | Statement: [Thunder Stone, associatedType, Electric]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedType Context triple: [Thunder Stone, associatedType, Electric]
-
A.
relatedType
chosen
Indicates that one entity is connected to another through a specified type or category of relationship.
-
B.
associatedEventType
Indicates that one entity is linked to another by the type or category of event with which it is associated.
-
C.
associatedUnitType
Indicates that one entity is linked to or characterized by a particular type or category of unit.
-
D.
associatedValue
Indicates that one entity is linked to another entity that serves as its corresponding or contextually related value.
-
E.
associatedWithAssociation
Indicates a relationship where an entity is linked or connected to a particular association or organization.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ad7ed548190a893110fa2ffb144 |
completed | April 20, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e55b11124c8190babacf2a0fe2d057 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:37 p.m.