Triple
T5877491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schwinger effect |
E130661
|
entity |
| Predicate | analogSystem |
P3882
|
FINISHED |
| Object | graphene |
—
|
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: graphene | Statement: [Schwinger effect, analogSystem, graphene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: analogSystem Context triple: [Schwinger effect, analogSystem, graphene]
-
A.
usedAsAnalogFor
chosen
Indicates that one entity is employed as a comparison or illustrative counterpart to help explain, represent, or understand another entity.
-
B.
isAnalogOrDigital
Indicates whether something operates using analog signals/representation or digital signals/representation.
-
C.
formerAnalogChannel
Indicates that an entity was previously an analog channel but no longer holds that status.
-
D.
conductingSystem
Indicates a relationship where one entity serves as the medium or pathway that transmits or conducts a signal, force, or substance for another entity.
-
E.
establishedSystem
Indicates that an entity has created, set up, or formally put into operation a particular system or structured arrangement.
- 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_69c0085523688190bfd487479ce819e6 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0432fea5881909f5c291dd8db6105 |
completed | March 22, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69c033499ca08190bd26cee5b03f6306 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:57 p.m.