Triple
T26765448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | up quark |
E674924
|
entity |
| Predicate | mesonExamplesContaining |
P58841
|
FINISHED |
| Object | pi-plus meson |
—
|
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: pi-plus meson | Statement: [up quark, mesonExamplesContaining, pi-plus meson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mesonExamplesContaining Context triple: [up quark, mesonExamplesContaining, pi-plus meson]
-
A.
hasExample
Indicates that one entity serves as an instance, illustration, or concrete example of another entity.
-
B.
baseExamples
Indicates that something serves as a fundamental or illustrative example for understanding or demonstrating another concept, item, or case.
-
C.
locationOfExamples
chosen
Indicates that something serves as the place or context where examples of a particular type, concept, or item can be found.
-
D.
hasExampleProvider
Indicates that one entity serves as an example provider or source of illustrative instances for another entity.
-
E.
hasExampleImplementation
Indicates that an entity is accompanied by a concrete implementation that serves as an example of how it can be realized or used.
- 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_69eecda85298819097ee1c38a3d772e7 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6192758648190ba2c0bfc9904994e |
completed | May 2, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:59 a.m.