Triple
T20453415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Player 001 |
E501712
|
entity |
| Predicate | contestantNumber |
P135676
|
FINISHED |
| Object | 001 |
—
|
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: 001 | Statement: [Player 001, contestantNumber, 001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contestantNumber Context triple: [Player 001, contestantNumber, 001]
-
A.
contestantOn
Indicates that one entity participates as a competitor in a contest, show, or competition associated with another entity.
-
B.
hasCompetitorNumber
chosen
Indicates that an entity is associated with a specific competitor identification number used to distinguish it in a competitive context.
-
C.
speakerNumber
Indicates the number of distinct speakers involved in a given speech, dialogue, or conversational instance.
-
D.
termNumberWon
Indicates the number of distinct terms or periods in which the subject has achieved a win or victory.
-
E.
featuresContestants
Indicates that something (such as an event, show, or competition) includes or presents certain individuals as contestants.
- 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_69e0b4ac0a1c81908845d0f8a56abce8 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e68d039af08190827bf765b50515a8 |
completed | April 20, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:32 a.m.