Triple
T26765354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lambda baryon |
E674922
|
entity |
| Predicate | isGroundStateOf |
P7814
|
FINISHED |
| Object | Lambda baryon family |
—
|
NE NERFINISHED |
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: Lambda baryon family | Statement: [Lambda baryon, isGroundStateOf, Lambda baryon family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGroundStateOf Context triple: [Lambda baryon, isGroundStateOf, Lambda baryon family]
-
A.
hasGroundState
chosen
Indicates that an entity possesses a lowest-energy, most stable state in its energy configuration.
-
B.
isGroundedIn
Indicates that something is based on, supported by, or justified through a particular source, foundation, or set of principles.
-
C.
usesGroundSystem
Indicates that one entity operates, relies on, or interacts with a particular ground-based system to perform its functions or services.
-
D.
isHomeGroundSince
Indicates that a particular location has served as the designated home ground of an entity (such as a team or organization) starting from a specified point in time.
-
E.
hasGroundPressure
Indicates that an entity exerts a specific amount of pressure on the ground or surface it is in contact with.
- 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_69eecda85298819097ee1c38a3d772e7 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6192758648190ba2c0bfc9904994e |
completed | May 2, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:59 a.m.