Triple
T22813627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belle detector |
E565044
|
entity |
| Predicate | hasMagnet |
P3957
|
FINISHED |
| Object | superconducting solenoid |
—
|
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: superconducting solenoid | Statement: [Belle detector, hasMagnet, superconducting solenoid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMagnet Context triple: [Belle detector, hasMagnet, superconducting solenoid]
-
A.
hasMagnetStatus
Indicates that an entity possesses a specific magnet-related state or designation within a given context.
-
B.
isMagnetFor
Indicates that one entity strongly attracts, draws in, or tends to gather another entity toward itself.
-
C.
usesMagnetType
chosen
Indicates that one entity employs or operates with a specific type of magnet in its function or configuration.
-
D.
hasMagneticMoment
Indicates that an entity possesses a magnetic moment, characterizing the strength and orientation of its magnetism.
-
E.
isPublicMagnetFor
Indicates that an entity functions as a publicly accessible magnet or attraction that draws attention, people, or resources toward it.
- 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17d61c6f081908d3911710b3aff51 |
completed | April 29, 2026, 3:39 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:32 p.m.