Triple
T31943668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V_us |
E815589
|
entity |
| Predicate | hasPhaseConvention |
P22945
|
FINISHED |
| Object | standard CKM phase convention |
—
|
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: standard CKM phase convention | Statement: [V_us, hasPhaseConvention, standard CKM phase convention]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhaseConvention Context triple: [V_us, hasPhaseConvention, standard CKM phase convention]
-
A.
hasPhaseRelation
Indicates that two entities are related by a specific phase difference or phase alignment in time or a cyclical process.
-
B.
hasPhaseCoefficient
Indicates that one entity is associated with a numerical coefficient quantifying its phase-related behavior or contribution in a given process or system.
-
C.
hasSignConvention
chosen
Indicates that a particular system, quantity, or representation follows a specified rule for assigning positive and negative signs.
-
D.
hasPhaseTransition
Indicates that an entity undergoes or exhibits a change from one physical phase or state of matter to another.
-
E.
hasMultiplePhases
Indicates that the related process, event, or activity occurs in more than one distinct phase or stage.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 12:06 a.m.