Triple
T34701355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1977 European Cup Final |
E1000376
|
entity |
| Predicate | hostClubCity |
P181705
|
FINISHED |
| Object | A.S. Roma |
—
|
NE NERFINISHED |
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: A.S. Roma | Statement: [1977 European Cup Final, hostClubCity, A.S. Roma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostClubCity Context triple: [1977 European Cup Final, hostClubCity, A.S. Roma]
-
A.
hostCityCluster
Indicates that a city serves as a central or primary host location within a defined group or cluster of related events, activities, or entities.
-
B.
hostTown
Indicates that one entity is the town or municipality that hosts, contains, or serves as the location for the other entity.
-
C.
hostCityInstanceOf
Indicates that a specific host city is an instance of a particular class or type of host city (e.g., Olympic host city, World Cup host city).
-
D.
hostBidCity
Indicates that a city is serving or proposed to serve as the host location for a bid (e.g., for an event, project, or competition).
-
E.
hostRepublic
Indicates that an entity serves as the host country or republic for another entity or event.
- 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_69f76dab937881909c86f1b9ad50445f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f7805c25dc8190b9977c561ba15975 |
completed | May 3, 2026, 5:05 p.m. |
Created at: May 3, 2026, 3:59 p.m.