Triple
T32187439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TRZ |
E822143
|
entity |
| Predicate | associatedCompanyPrimaryAssetType |
P63924
|
FINISHED |
| Object | office buildings |
—
|
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: office buildings | Statement: [TRZ, associatedCompanyPrimaryAssetType, office buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCompanyPrimaryAssetType Context triple: [TRZ, associatedCompanyPrimaryAssetType, office buildings]
-
A.
associatedCompanyMainProductLine
Indicates that a company’s primary or main line of products is linked or related to a specified product category or product line.
-
B.
relatedCompanyType
Indicates the type or nature of the relationship that one company has to another company.
-
C.
associatedCompanyKnownFor
Indicates that a company linked to an entity is recognized or notable for a particular product, service, activity, or characteristic.
-
D.
associatedCompanySpecialization
chosen
Indicates that a company is linked to a particular area of specialization or expertise.
-
E.
associatedCompanyCommonName
Indicates that there is a relationship where a company is linked to a commonly used or publicly recognized version of its name.
- 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_69f3490819cc81909bae1f8ce99423c5 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:35 a.m.