Triple
T30705705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petrovsky Stadium |
E781745
|
entity |
| Predicate | hasTenantUntil |
P102890
|
FINISHED |
| Object | FC Zenit Saint Petersburg 2017 |
—
|
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 Zenit Saint Petersburg 2017 | Statement: [Petrovsky Stadium, hasTenantUntil, FC Zenit Saint Petersburg 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTenantUntil Context triple: [Petrovsky Stadium, hasTenantUntil, FC Zenit Saint Petersburg 2017]
-
A.
hasTenantSince
Indicates that an entity has been the tenant of another entity starting from a specified point in time.
-
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.
hasTenants
Indicates that an entity occupies or rents space from another entity as its tenant.
-
D.
hasFormerPrimaryTenant
Indicates that an entity previously served as the main or principal tenant of another entity, but no longer holds that status.
-
E.
hasRemainingLifespan
Indicates that an entity still has a certain amount of time or capacity left before it reaches the end of its expected lifespan or usability.
- 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_69f224abfcf081909492e64d3cc35262 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: April 29, 2026, 8:35 p.m.