Triple
T16473425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Young Lions |
E400124
|
entity |
| Predicate | statusInTournaments |
P83772
|
FINISHED |
| Object | perennial contender |
—
|
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: perennial contender | Statement: [Young Lions, statusInTournaments, perennial contender]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInTournaments Context triple: [Young Lions, statusInTournaments, perennial contender]
-
A.
scoredInTournament
Indicates that an entity achieved a score or points during a particular tournament.
-
B.
statusInCompetition
chosen
Indicates the current standing or role an entity holds within a specific competition or contest.
-
C.
hasTournament
Indicates that an entity organizes, hosts, or is associated with a specific tournament.
-
D.
playedInTournament
Indicates that an entity participated as a competitor or player in a specific tournament.
-
E.
hasTournamentRecord
Indicates that an entity possesses a documented performance or results record in a specific tournament or set of tournaments.
- 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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32dd266c48190991a1484eb2f7bcc |
completed | April 18, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69e22706b0588190a48a951c5211a617 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:11 a.m.