Triple
T14991237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | g-2 |
E373838
|
entity |
| Predicate | hasDiscrepancyWith |
P113438
|
FINISHED |
| Object | some Standard Model calculations |
—
|
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: some Standard Model calculations | Statement: [g-2, hasDiscrepancyWith, some Standard Model calculations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiscrepancyWith Context triple: [g-2, hasDiscrepancyWith, some Standard Model calculations]
-
A.
foundInconsistentWith
chosen
Indicates that one entity has been determined to conflict with, contradict, or fail to align with another entity.
-
B.
differIn
Indicates that two entities are not the same in at least one specified aspect, attribute, or value.
-
C.
isInconsistent
Indicates that there is a logical or factual contradiction within or between the entities or statements involved.
-
D.
allegedInconsistencyWith
Indicates a claimed or suspected contradiction or mismatch between one thing and another.
-
E.
inconsistencyDiscoveredIn
Indicates that an inconsistency has been identified within or associated with a specified entity, context, or dataset.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded715db408190b44e8a8452c79764 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:53 a.m.