Triple
T37865636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prudential Plaza |
E944461
|
entity |
| Predicate | complexNameOf |
P189300
|
FINISHED |
| Object | One Prudential Plaza |
—
|
NE NERFINISHED |
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: One Prudential Plaza | Statement: [Prudential Plaza, complexNameOf, One Prudential Plaza]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: complexNameOf Context triple: [Prudential Plaza, complexNameOf, One Prudential Plaza]
-
A.
complexName
Indicates that an entity has a multi-part or structurally intricate name, typically composed of several elements or components.
-
B.
commonNameOf
Indicates that one entity is the commonly used or popular name by which the other entity is known.
-
C.
exportName
Indicates that one entity is exported under a specific name or label in relation to another context or system.
-
D.
importName
Indicates that one entity brings another entity into a scope, module, or context under a specific name used for reference.
-
E.
exampleCompoundName
Indicates that something serves as an illustrative or representative compound name used for demonstration or example purposes.
- 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_69f76eee2f9c8190b1272aa2ee55ebf5 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69fbbae3fc508190adff3d7abbf107a4 |
completed | May 6, 2026, 10:04 p.m. |
Created at: May 3, 2026, 4:19 p.m.