Triple
T18465092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donbass Arena |
E451137
|
entity |
| Predicate | mainTenantUntil |
P102890
|
FINISHED |
| Object | FC Shakhtar Donetsk 2014 |
—
|
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: FC Shakhtar Donetsk 2014 | Statement: [Donbass Arena, mainTenantUntil, FC Shakhtar Donetsk 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainTenantUntil Context triple: [Donbass Arena, mainTenantUntil, FC Shakhtar Donetsk 2014]
-
A.
mainTenant
Indicates that the subject is the primary tenant responsible for a property or rental agreement, as opposed to a subtenant or secondary occupant.
-
B.
primaryTenantUntil
chosen
Indicates that an entity serves as the main or principal tenant of a property or lease up to a specified end date.
-
C.
tenantsEnd
Indicates that a tenancy or lease relationship between parties comes to an end at a specified time or under certain conditions.
-
D.
intendedTenant
Indicates that one entity is designated or expected to occupy or lease another entity (such as a property) as a tenant.
-
E.
tenantBecame
Indicates that an entity transitioned into the role or status of a tenant at a particular time or under specific conditions.
- 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e52a82920081909b2b89125db5982a |
completed | April 19, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69e469d05cf4819099baf1665a9cf18a |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:34 a.m.