Triple
T3921379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fermion |
E88965
|
entity |
| Predicate | hasChargeOptions |
P8394
|
FINISHED |
| Object | Can be electrically charged or neutral |
—
|
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: Can be electrically charged or neutral | Statement: [Fermion, hasChargeOptions, Can be electrically charged or neutral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChargeOptions Context triple: [Fermion, hasChargeOptions, Can be electrically charged or neutral]
-
A.
hasCharge
chosen
Indicates that an entity possesses a specific electrical or formal charge, such as positive, negative, or neutral.
-
B.
hasPaymentOption
Indicates that an entity supports or offers a particular method or option for making payments.
-
C.
featuresCharge
Indicates that one entity includes, offers, or is characterized by a particular charge (such as a fee, cost, or pricing component).
-
D.
isFreeOfCharge
Indicates that no payment or fee is required for the associated action, service, or item.
-
E.
hasAdvancePaymentOption
Indicates that an entity offers the possibility to pay, in full or in part, before the corresponding goods or services are delivered or consumed.
- 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_69aed955229881909e85e73ffab1d343 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef188b474819087680db42b04ecdd |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee75eedcc81908088ff4dbb8be56b |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.