Triple
T23902527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sakata model |
E601091
|
entity |
| Predicate | postulatesFundamentalConstituent |
P40225
|
FINISHED |
| Object | proton |
—
|
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: proton | Statement: [Sakata model, postulatesFundamentalConstituent, proton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postulatesFundamentalConstituent Context triple: [Sakata model, postulatesFundamentalConstituent, proton]
-
A.
hasPostulate
Indicates that one entity includes, relies on, or is based upon a particular postulate asserted by another entity or within a given framework.
-
B.
isFundamental
Indicates that something is a basic, essential, or foundational element upon which other things depend or are built.
-
C.
proposesExistenceOf
chosen
Indicates that one entity puts forward or suggests that another entity should exist or be brought into existence.
-
D.
proposesHypothesis
Indicates that one entity puts forward a tentative explanation or hypothesis for consideration regarding another entity or phenomenon.
-
E.
foundationAxiomHoldsIn
Indicates that the foundation (or regularity) axiom is satisfied within a given model, structure, or context.
- 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_69e295364a488190bcac702e9bb7f764 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cddf46948190b8625811725fe41d |
completed | April 29, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:26 p.m.