Triple
T2469605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emery Roth & Sons |
E55337
|
entity |
| Predicate | notableClientType |
P7186
|
FINISHED |
| Object | corporate clients |
—
|
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: corporate clients | Statement: [Emery Roth & Sons, notableClientType, corporate clients]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableClientType Context triple: [Emery Roth & Sons, notableClientType, corporate clients]
-
A.
notableClient
chosen
Indicates that one entity serves as a prominent or distinguished client of another entity.
-
B.
notableTargetType
Indicates that the subject is notable or significant specifically in relation to entities of the given target type.
-
C.
notableServiceType
Indicates that the subject is associated with a particular type or category of service that is especially notable or significant.
-
D.
notableProjectType
Indicates the type or category of a project for which an entity is particularly well-known or notable.
-
E.
clientOf
Indicates that one entity receives services or conducts business from another entity in a client–provider relationship.
- 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_69ab49e3622c8190ad22afa2c4fbb807 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd2bc7b5481908b3664495e99f1a4 |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0b3ea308190a6d8499c2a542c50 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:44 p.m.