Triple
T2655282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helmet Catch |
E54592
|
entity |
| Predicate | tyreePosition |
P17745
|
FINISHED |
| Object | wide receiver |
—
|
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: wide receiver | Statement: [Helmet Catch, tyreePosition, wide receiver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tyreePosition Context triple: [Helmet Catch, tyreePosition, wide receiver]
-
A.
positionCoached
Indicates that one entity served as a coach for another entity in a specific position or role.
-
B.
positionOnTrident
Indicates that one entity occupies a specific location or slot on a trident-like structure or configuration.
-
C.
positionB
Indicates that one entity occupies or is located at a specific position relative to another entity.
-
D.
positionInFormation
chosen
Indicates the relative place or role an entity occupies within an organized formation or arrangement.
-
E.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
- 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_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. |
Created at: March 6, 2026, 9:53 p.m.