Triple
T26765555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Σ*(1385) |
E674926
|
entity |
| Predicate | isDescribedByTheory |
P65908
|
FINISHED |
| Object | quantum chromodynamics |
—
|
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: quantum chromodynamics | Statement: [Σ*(1385), isDescribedByTheory, quantum chromodynamics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDescribedByTheory Context triple: [Σ*(1385), isDescribedByTheory, quantum chromodynamics]
-
A.
hasTheory
chosen
Indicates that an entity possesses, is associated with, or is characterized by a particular theory.
-
B.
reflectsTheoryOf
Indicates that one entity embodies, expresses, or is based on the theoretical framework, principles, or assumptions developed by another entity.
-
C.
hasTheoreticalStatus
Indicates that something possesses a particular theoretical standing, classification, or role within a conceptual or theoretical framework.
-
D.
namedForTheory
Indicates that something is named in honor of, or derived from, a particular theory.
-
E.
occursInTheory
Indicates that an event, concept, or phenomenon is situated, described, or analyzed within a particular theoretical framework or theory.
- 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.