Triple
T26765504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | charm quark |
E674925
|
entity |
| Predicate | formsBoundStatesWith |
P170632
|
FINISHED |
| Object | up quark |
—
|
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: up quark | Statement: [charm quark, formsBoundStatesWith, up quark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsBoundStatesWith Context triple: [charm quark, formsBoundStatesWith, up quark]
-
A.
statesBoundOfForm
Indicates that one state or condition serves as a boundary or limiting form for another.
-
B.
isBoundStateOf
Indicates that one entity is a bound or confined condition, configuration, or state associated with another entity.
-
C.
areBoundFrom
Indicates that one entity is constrained, limited, or restricted starting from a specified point, source, or condition.
-
D.
formsBoundaryType
Indicates that one entity serves as a specific type of boundary for another entity.
-
E.
isInitiallyBoundWith
Indicates that two or more entities are connected, associated, or constrained together at the starting point of a process, state, or interaction.
- F. None of above. chosen
Provenance (4 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_69eecda85298819097ee1c38a3d772e7 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f693ffa7908190aa4c451b16df9be6 |
completed | May 3, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f6938244648190a553b532387b812c |
completed | May 3, 2026, 12:14 a.m. |
Created at: April 27, 2026, 3:59 a.m.