Triple
T2655257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helmet Catch |
E54592
|
entity |
| Predicate | passType |
P42000
|
FINISHED |
| Object | deep pass over the middle |
—
|
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: deep pass over the middle | Statement: [Helmet Catch, passType, deep pass over the middle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passType Context triple: [Helmet Catch, passType, deep pass over the middle]
-
A.
permitType
Indicates the specific category or kind of permit associated with an entity or activity.
-
B.
admissionType
Indicates the category or manner in which an entity (such as a person or case) is formally accepted or admitted into a system, institution, or process.
-
C.
patronType
Indicates the classification or category of a patron in relation to a service, institution, or resource.
-
D.
securityType
Indicates the classification or category of security associated with an entity, such as the type of financial instrument, protection mechanism, or access control applied.
-
E.
validityType
Indicates the specific kind or category of validity that characterizes how or under what conditions something is considered valid.
- 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abda0ba2208190ad87763ecbef8c3c |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd815d06481909535c02b0aba8553 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abda0a13308190a986df86270258a7 |
completed | March 7, 2026, 7:55 a.m. |
Created at: March 6, 2026, 9:53 p.m.