Triple
T16144374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Armstrong |
E391739
|
entity |
| Predicate | scoredGoal |
P2220
|
FINISHED |
| Object | clinching goal in 1967 Stanley Cup Finals Game 6 |
—
|
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: clinching goal in 1967 Stanley Cup Finals Game 6 | Statement: [George Armstrong, scoredGoal, clinching goal in 1967 Stanley Cup Finals Game 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scoredGoal Context triple: [George Armstrong, scoredGoal, clinching goal in 1967 Stanley Cup Finals Game 6]
-
A.
scoredGameWinningGoal
chosen
Indicates that an entity scored the decisive goal that determined the final victory in a game.
-
B.
ownGoalBy
Indicates that a goal was accidentally scored against a team by the specified player (i.e., the player scored an own goal).
-
C.
officialGoal
Indicates that something is the formally designated or institutionally recognized objective or target of an entity.
-
D.
scoredGoalsInFinalOf
Indicates that one entity scored one or more goals in the final match of a specified competition or event.
-
E.
scoredFor
Indicates that one entity achieved points or a score on behalf of another entity, such as a player scoring for a team.
- 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21d92b0408190a010bd8e5193aa36 |
completed | April 17, 2026, 11:46 a.m. |
| PD | Predicate disambiguation | batch_69e182885bc08190822ae7e8a4b8ac1f |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.