Triple
T27797535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglo-Italian Cup |
E702154
|
entity |
| Predicate | hadRevivedProfessionalEra |
P63739
|
FINISHED |
| Object | 1992–1996 |
—
|
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: 1992–1996 | Statement: [Anglo-Italian Cup, hadRevivedProfessionalEra, 1992–1996]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadRevivedProfessionalEra Context triple: [Anglo-Italian Cup, hadRevivedProfessionalEra, 1992–1996]
-
A.
revivedAfter
Indicates that one entity comes back to life or is restored to a living or active state after a period of being dead, inactive, or nonfunctional, following another event or time point.
-
B.
revivedAs
Indicates that an entity, after having ceased to exist or function in its original form, comes back into existence or operation in a new or restored form.
-
C.
revivedAtLevel
Indicates that an entity was brought back to life or reactivated when a specified level or stage was reached.
-
D.
hasRevivalsIn
chosen
Indicates that something has been brought back, renewed, or reintroduced in specific times, places, or contexts.
-
E.
isFrequentlyRevived
Indicates that an entity is brought back, restored, or reintroduced many times over a period.
- 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6380c776c8190afe636c9e65301a0 |
completed | May 2, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 5:32 p.m.