Triple
T4826923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thames Ironworks F.C. |
E107846
|
entity |
| Predicate | playedFirstMatch |
P13507
|
FINISHED |
| Object | 1895 |
—
|
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: 1895 | Statement: [Thames Ironworks F.C., playedFirstMatch, 1895]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedFirstMatch Context triple: [Thames Ironworks F.C., playedFirstMatch, 1895]
-
A.
firstGamePlayed
chosen
Indicates the specific game that an entity participated in before any other, marking the earliest game in which it played.
-
B.
firstPlayed
Indicates that one entity was the earliest or initial thing (such as a song, game, or media item) that another entity engaged with or played.
-
C.
openingMatch
Indicates that one entity serves as the initial or first match, game, or contest in a series, event, or competition involving another entity.
-
D.
playedInTournament
Indicates that an entity participated as a competitor or player in a specific tournament.
-
E.
eraPlayed
Indicates the historical or stylistic time period during which something (typically a work or performance) was played or took place.
- 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_69bd43fac8188190803f0327190621e4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1fe130819087ae01309f96a0c8 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:24 p.m.