Triple
T6648705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rugby League World Cup trophy |
E150764
|
entity |
| Predicate | recovered |
P72037
|
FINISHED |
| Object | 1990 |
—
|
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: 1990 | Statement: [Rugby League World Cup trophy, recovered, 1990]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recovered Context triple: [Rugby League World Cup trophy, recovered, 1990]
-
A.
recoveredIn
Indicates that something lost, damaged, or impaired has been restored or regained within a particular context, process, or location.
-
B.
recoveredFrom
Indicates that an entity has returned to a normal or improved state after previously experiencing or being affected by another specified condition, event, or problem.
-
C.
recovery
Indicates the process or state in which an entity regains a previous condition, function, or status after loss, damage, or decline.
-
D.
restored
Indicates that an entity has returned another entity to a previous or improved state, condition, or position after damage, loss, or alteration.
-
E.
remainsRecoveredFrom
Indicates that physical remains of an entity have been found and retrieved from a specified source, location, or context.
- F. None of above. chosen
Provenance (4 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_69c687f1a3048190828b7342f7125d5c |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad04d66c8190926ffcbff372643b |
completed | March 27, 2026, 4:15 p.m. |
| PDg | Predicate description generation | batch_69c6cc988c0081909d22b86ca299331c |
completed | March 27, 2026, 6:29 p.m. |
Created at: March 27, 2026, 2 p.m.