Triple
T24364321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1995 Rugby League World Cup |
E614152
|
entity |
| Predicate | tournamentNumber |
P147795
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [1995 Rugby League World Cup, tournamentNumber, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tournamentNumber Context triple: [1995 Rugby League World Cup, tournamentNumber, 10]
-
A.
editionNumberOfTournament
chosen
Indicates the specific sequential edition number assigned to a given tournament within its overall series or history.
-
B.
numberOfTournaments
Indicates the total count of tournaments associated with or participated in by an entity.
-
C.
tournamentMatches
Indicates that a tournament includes or schedules specific matches as part of its competitive structure.
-
D.
tournamentSpecific
Indicates that the relationship, condition, or data applies only within the context of a particular tournament and not generally across other contexts or events.
-
E.
tourEvent
Indicates an event that is part of a tour, such as a scheduled stop, performance, or appearance within a larger touring itinerary.
- 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_69e2d7dfe7f08190b7a1f3a36483ab05 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2938694548190a3fcb148cfff65b0 |
completed | April 29, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:01 a.m.