Triple
T24015864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shinagawa Intercity |
E594671
|
entity |
| Predicate | targetTenant |
P96896
|
FINISHED |
| Object | large corporations |
—
|
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: large corporations | Statement: [Shinagawa Intercity, targetTenant, large corporations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetTenant Context triple: [Shinagawa Intercity, targetTenant, large corporations]
-
A.
intendedTenant
chosen
Indicates that one entity is designated or expected to occupy or lease another entity (such as a property) as a tenant.
-
B.
tenantedBy
Indicates that a property, land, or space is occupied or leased by a specific tenant.
-
C.
mainTenant
Indicates that the subject is the primary tenant responsible for a property or rental agreement, as opposed to a subtenant or secondary occupant.
-
D.
primaryTenantFrom
Indicates that one entity serves as the main or principal tenant associated with another entity (such as a property or lease).
-
E.
anchorTenant
Indicates that an entity serves as a primary or major tenant whose presence helps attract other tenants or users to a shared space or platform.
- 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_69e288bc8f608190ac4af29f0bd1c744 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d5a3f5a08190b7170270c4fcf080 |
completed | April 29, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:42 p.m.