Triple
T5229618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dirac field |
E118074
|
entity |
| Predicate | isUsedToModel |
P35898
|
FINISHED |
| Object | baryons at fundamental level (quark fields) |
—
|
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: baryons at fundamental level (quark fields) | Statement: [Dirac field, isUsedToModel, baryons at fundamental level (quark fields)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedToModel Context triple: [Dirac field, isUsedToModel, baryons at fundamental level (quark fields)]
-
A.
usedToModel
chosen
Indicates that one entity serves as a model or representation for another entity, typically for purposes of analysis, simulation, or understanding.
-
B.
useOfModel
Indicates that one entity employs, applies, or relies on a particular model for a specific purpose or task.
-
C.
usedByModel
Indicates that something (such as a resource, method, or component) is utilized or consumed by a particular model.
-
D.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
E.
notUsedOnModel
Indicates that a particular item, component, or feature is not applied, installed, or utilized on the specified model.
- 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_69bd4466fb8c819083b806a79414d7e4 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b0093a88190aba381ba3f761408 |
completed | March 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69bd77bf1ef08190bb3487b3f3ee088c |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:48 p.m.