Triple
T37464071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zilliax |
E930989
|
entity |
| Predicate | hasMagnetic |
P61878
|
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: [Zilliax, hasMagnetic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMagnetic Context triple: [Zilliax, hasMagnetic, true]
-
A.
hasMagneticMoment
Indicates that an entity possesses a magnetic moment, characterizing the strength and orientation of its magnetism.
-
B.
usesMagnetType
Indicates that one entity employs or operates with a specific type of magnet in its function or configuration.
-
C.
hasMagneticDualObject
Indicates that one object is the magnetic dual counterpart of another object in a physical or mathematical theory.
-
D.
hasMagnetStatus
chosen
Indicates that an entity possesses a specific magnet-related state or designation within a given context.
-
E.
isMagnetFor
Indicates that one entity strongly attracts, draws in, or tends to gather another entity toward itself.
- 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_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.