Triple
T19573388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hannes Löhr |
E489780
|
entity |
| Predicate | numberOfMatchesInLeague |
P51305
|
FINISHED |
| Object | 381 |
—
|
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: 381 | Statement: [Hannes Löhr, numberOfMatchesInLeague, 381]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfMatchesInLeague Context triple: [Hannes Löhr, numberOfMatchesInLeague, 381]
-
A.
capacityLeagueMatches
Indicates the maximum number of league matches that can be held or accommodated, typically by a venue, schedule, or organizational structure.
-
B.
leagueMatchesPlayed
chosen
Indicates the number of matches an entity has participated in within a specific league competition.
-
C.
numberOfTestMatches
Indicates the total count of test matches associated with a given entity (such as a player, team, or series) in the relationship.
-
D.
numberOfFinalMatches
Indicates the total count of final-stage matches associated with a given entity or event.
-
E.
totalMatchesPlayed
Indicates the total number of matches that have been played by the referenced entity or between the related entities.
- 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6402228488190b5649d4bbd34d019 |
completed | April 20, 2026, 3:02 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:42 p.m.