Triple
T22648152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hull–Hedberg–Nilsson line |
E559019
|
entity |
| Predicate | offensiveRole |
P78138
|
FINISHED |
| Object | top scoring line |
—
|
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: top scoring line | Statement: [Hull–Hedberg–Nilsson line, offensiveRole, top scoring line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offensiveRole Context triple: [Hull–Hedberg–Nilsson line, offensiveRole, top scoring line]
-
A.
playsRoleInOffense
chosen
Indicates that an entity performs a specific function or position within an offensive strategy or system.
-
B.
defensiveRole
Indicates that an entity serves a protective or guarding function in relation to another entity or context.
-
C.
offensiveTackle
Indicates that an entity plays the offensive tackle position, responsible for blocking and protecting on the offensive line in a gridiron football context.
-
D.
offensiveStrategy
Indicates a strategic approach focused on attacking or aggressively advancing against an opponent.
-
E.
offensiveStrength
Indicates the degree or capacity of an entity to carry out effective attacks or aggressive actions against an opponent.
- 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_69e245489dd88190b1f674acf61c8769 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f17039c2bc8190972a7c169b27005c |
completed | April 29, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:05 p.m.