Triple
T24626278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Incheon SSG Landers Field |
E609548
|
entity |
| Predicate | previousPrimaryTenant |
P156794
|
FINISHED |
| Object | SK Wyverns |
—
|
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: SK Wyverns | Statement: [Incheon SSG Landers Field, previousPrimaryTenant, SK Wyverns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousPrimaryTenant Context triple: [Incheon SSG Landers Field, previousPrimaryTenant, SK Wyverns]
-
A.
primaryTenantTo
Indicates that one entity serves as the main or principal tenant in relation to another entity, such as a property or lease.
-
B.
futurePrimaryTenant
Indicates that an entity is designated to become the primary tenant of a property or resource at a future time.
-
C.
primaryTenantFrom
Indicates that one entity serves as the main or principal tenant associated with another entity (such as a property or lease).
-
D.
currentPrimaryTenant
Indicates that the subject is the main tenant currently holding primary tenancy rights or responsibilities for the referenced property or unit.
-
E.
primaryTenantRole
Indicates that an entity holds the main or leading tenant role in a tenancy relationship.
- 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_69e2c4d1d3708190a0f2dc6a3a8523bb |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6d0ab708190b2e3b94dd20ca76b |
completed | April 30, 2026, 12:48 a.m. |
| PDg | Predicate description generation | batch_69f2b8b8bc5881908df49c0b07110246 |
completed | April 30, 2026, 2:04 a.m. |
Created at: April 18, 2026, 2:32 a.m.