Triple
T21209326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zeller Realty Group |
E522677
|
entity |
| Predicate | typeOfClient |
P809
|
FINISHED |
| Object | institutional investors |
—
|
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: institutional investors | Statement: [Zeller Realty Group, typeOfClient, institutional investors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfClient Context triple: [Zeller Realty Group, typeOfClient, institutional investors]
-
A.
clientOf
Indicates that one entity receives services or conducts business from another entity in a client–provider relationship.
-
B.
customerType
chosen
Indicates the classification or category assigned to a customer based on their characteristics, status, or relationship with a business.
-
C.
operatedForClientType
Indicates that an operation or service is performed specifically on behalf of, or tailored to, a particular type or category of client.
-
D.
typeOfIdentity
Indicates the specific category or nature of identity that characterizes or defines an entity within a given context.
-
E.
clientFor
Indicates that one entity acts as a client that uses the services, resources, or interface provided by another entity.
- 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_69e0b5112d8881909510b2dcdc93106d |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73436eb4c819082e05caf1ba52672 |
completed | April 21, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:26 p.m.