Triple
T8982099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HK433 |
E214554
|
entity |
| Predicate | ejectionPattern |
P49676
|
FINISHED |
| Object | right-side ejection |
—
|
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: right-side ejection | Statement: [HK433, ejectionPattern, right-side ejection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ejectionPattern Context triple: [HK433, ejectionPattern, right-side ejection]
-
A.
involvesParticleEjection
Indicates that the action or process includes the emission or release of particles from a source.
-
B.
hasEjecta
chosen
Indicates that one entity produces or is associated with material expelled or thrown out from another entity as a result of an energetic event or process.
-
C.
airingPattern
Indicates the recurring schedule or pattern according to which something (such as a program or content) is broadcast or made available.
-
D.
escapementType
Indicates the specific mechanism or method by which motion or energy is intermittently released or regulated in a system.
-
E.
transmissionPattern
Indicates how something is passed or spread from one entity to another, such as the mode or route of transmission.
- 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_69ca839ea8b88190922c6a326ffcc0d3 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc67a891e881909e4b84ed82491651 |
completed | April 1, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69cc5edba0f88190b97401636a076d7a |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:03 p.m.