Triple
T30415452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Positive Electron |
E773740
|
entity |
| Predicate | reportedDiscoveryOf |
P27994
|
FINISHED |
| Object | positron |
—
|
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: positron | Statement: [The Positive Electron, reportedDiscoveryOf, positron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportedDiscoveryOf Context triple: [The Positive Electron, reportedDiscoveryOf, positron]
-
A.
reportsDiscoveryOf
chosen
Indicates that one entity formally announces or documents the finding or uncovering of another entity (typically a new object, fact, or phenomenon).
-
B.
madeDiscoveryOn
Indicates that an entity discovered or identified something on a specific date or at a specific point in time.
-
C.
discoveredAs
Indicates that one entity was first identified, found, or recognized in the role or form specified by another entity.
-
D.
discoveredFeature
Indicates that an entity has identified or uncovered a previously unknown or unrecognized feature of another entity or object.
-
E.
reportedFor
Indicates that one entity has formally notified an authority or system about another entity’s behavior, condition, or status, typically to trigger review or action.
- 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_69f22490b8b48190ab10c886a8d58c89 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:05 p.m.