Triple
T7600547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omega minus baryon |
E179970
|
entity |
| Predicate | confinement |
P76190
|
FINISHED |
| Object | quark confinement |
—
|
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: quark confinement | Statement: [Omega minus baryon, confinement, quark confinement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confinement Context triple: [Omega minus baryon, confinement, quark confinement]
-
A.
isConfined
chosen
Indicates that an entity is restricted to a limited space or area, unable to move freely beyond defined boundaries.
-
B.
restriction
Indicates a limiting condition or rule that constrains or controls what an entity can do, use, or access in relation to another entity or context.
-
C.
heldInSolitaryConfinement
Indicates that an entity is subjected to isolation from others, typically as a form of confinement or punishment, where they are kept alone for extended periods.
-
D.
closure
Indicates that an entity is closed or not accessible/available for use, entry, or interaction.
-
E.
usesConstriction
Indicates that one entity applies pressure by tightening or squeezing around another entity to restrain, control, or affect it.
- 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_69c69f3487ec8190bf7acdf2dd91e6d6 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9d9c55c8190841f3bf3225c096a |
completed | March 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e2e42c8190afc802c4796c9cc2 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:53 p.m.