Triple
T4345479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monte Carlo Rally |
E97888
|
entity |
| Predicate | wasRoundOf |
P15100
|
FINISHED |
| Object | World Rally Championship since 1973 (with some gaps) |
—
|
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: World Rally Championship since 1973 (with some gaps) | Statement: [Monte Carlo Rally, wasRoundOf, World Rally Championship since 1973 (with some gaps)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasRoundOf Context triple: [Monte Carlo Rally, wasRoundOf, World Rally Championship since 1973 (with some gaps)]
-
A.
playoffRound
Indicates the specific stage or round within a playoff series in which a game, matchup, or event takes place.
-
B.
hasRound
chosen
Indicates that an entity possesses, includes, or is associated with a particular round (e.g., a round of an event, game, or process).
-
C.
wonTournament
Indicates that an entity emerged as the overall victor in a tournament competition.
-
D.
secondRoundWinner
Indicates that the subject is the winner of the second round in a multi-round competition, contest, or process.
-
E.
draftRound
Indicates the specific round in which an entity was selected during a drafting or selection process.
- 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_69b34548402c819085ab68b27c235a87 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3518bec408190ba07643bbf7eb632 |
completed | March 12, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69b34f4fe1c481908d6d66e15697c04b |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:15 p.m.