Triple
T6064269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NA64 |
E135115
|
entity |
| Predicate | physicsFocus |
P24329
|
FINISHED |
| Object | physics beyond the Standard Model |
—
|
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: physics beyond the Standard Model | Statement: [NA64, physicsFocus, physics beyond the Standard Model]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: physicsFocus Context triple: [NA64, physicsFocus, physics beyond the Standard Model]
-
A.
researchTopic
chosen
Indicates that a subject conducts or focuses research on a particular topic or area of study.
-
B.
secondScience
Indicates that the subject is the second entity in a sequence or ranking specifically within a scientific context or domain.
-
C.
physicalBasis
Indicates that one entity serves as the underlying physical foundation, mechanism, or substrate that gives rise to or supports the properties, behavior, or existence of another entity.
-
D.
focusType
Indicates the specific kind or category of focus or attention that is being applied to or associated with an entity or interaction.
-
E.
categoryFocus
Indicates that one entity is the primary subject, theme, or focal point within the broader category defined by the other entity.
- 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_69c00878d06881909ee78e88913bf890 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05723c91c819090b4d4672e72f9f3 |
completed | March 22, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69c049f031408190b08b2766237c5dd0 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:10 p.m.