Triple
T3730269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Invincibles (Arsenal 2003–04) |
E79043
|
entity |
| Predicate | unbeatenRunLeagueMatches |
P17261
|
FINISHED |
| Object | 38 |
—
|
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: 38 | Statement: [The Invincibles (Arsenal 2003–04), unbeatenRunLeagueMatches, 38]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unbeatenRunLeagueMatches Context triple: [The Invincibles (Arsenal 2003–04), unbeatenRunLeagueMatches, 38]
-
A.
unbeatenLeagueSeason
chosen
Indicates that a team completed an entire league season without losing any match.
-
B.
unbeatenStreakYears
Indicates the number of consecutive years during which an entity has remained unbeaten or undefeated.
-
C.
longestUnbeatenStreak
Indicates the relationship where an entity holds the greatest continuous sequence of events (such as games or matches) without a loss compared to others.
-
D.
notableStreakMatch
Indicates that a match is part of a significant or noteworthy streak (such as consecutive wins, losses, or performances) associated with an entity.
-
E.
consecutiveGamesPlayed
Indicates that an entity has participated in a series of games without interruption, one immediately following another.
- 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.