Triple
T3730273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Invincibles (Arsenal 2003–04) |
E79043
|
entity |
| Predicate | topLeagueScorerGoals |
P43996
|
FINISHED |
| Object | 30 |
—
|
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: 30 | Statement: [The Invincibles (Arsenal 2003–04), topLeagueScorerGoals, 30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topLeagueScorerGoals Context triple: [The Invincibles (Arsenal 2003–04), topLeagueScorerGoals, 30]
-
A.
topScorer
Indicates that the subject is the individual with the highest score among a specified group or in a particular context.
-
B.
topScorerPoints
Indicates the number of points scored by the top-scoring entity in a given context or event.
-
C.
goalScorer
Indicates that the subject is the player who scored a particular goal in a game or match.
-
D.
scoringLeaderGoals
chosen
Indicates that the subject is the leading scorer in terms of goals, having scored more goals than any other relevant participant in the given context.
-
E.
totalGoalsRecord
Indicates the total number of goals that have been recorded for an entity across all relevant events or contexts.
- 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_69ad8b0e4650819090ad7cef094285e8 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb1bb5408190990ea4dfbdab5c68 |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc04746588190b0dc535638f23546 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.