Triple
T4424822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | arXiv |
E95183
|
entity |
| Predicate | hasNotableFieldImpact |
P39276
|
FINISHED |
| Object | high-energy physics |
—
|
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: high-energy physics | Statement: [arXiv, hasNotableFieldImpact, high-energy physics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableFieldImpact Context triple: [arXiv, hasNotableFieldImpact, high-energy physics]
-
A.
hasNotableImpact
Indicates that one entity exerts a significant or noteworthy influence or effect on another entity or context.
-
B.
hasNotableDelta
Indicates that there is a significant or noteworthy change or difference between two compared entities or states.
-
C.
hasUpstreamImpactOn
Indicates that one entity’s actions, changes, or outputs affect another entity that is positioned earlier in a process, flow, or dependency chain.
-
D.
hasNotableIssue
Indicates that an entity is associated with a significant problem, concern, or defect that is noteworthy or exceptional compared to typical cases.
-
E.
notableField
chosen
Indicates the field, discipline, or area of activity for which an entity is especially known or distinguished.
- 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_69b3453c2a0c8190926b574c90766db9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3554ca5208190ba2661616dcf071c |
completed | March 13, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69b34f5eabe88190a12b244ea71e46d6 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:30 p.m.