Triple
T32187436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TRZ |
E822143
|
entity |
| Predicate | associatedCompanyStructure |
P206220
|
FINISHED |
| Object | REIT |
—
|
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: REIT | Statement: [TRZ, associatedCompanyStructure, REIT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCompanyStructure Context triple: [TRZ, associatedCompanyStructure, REIT]
-
A.
relatedCompanyType
Indicates the type or nature of the relationship that one company has to another company.
-
B.
associatedCompanyGlobalScope
Indicates that there is a relationship linking an entity to a company at a global (worldwide) organizational scope.
-
C.
associatedCompanyKnownFor
Indicates that a company linked to an entity is recognized or notable for a particular product, service, activity, or characteristic.
-
D.
partnerStructure
Indicates a relationship where one entity is organized, configured, or structured in coordination with, or as a counterpart to, another entity in a partnership context.
-
E.
linkedCompany
Indicates that two companies are connected through some defined relationship, such as ownership, partnership, or shared control.
- 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_69f3490819cc81909bae1f8ce99423c5 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 12:35 a.m.