Triple
T27538657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Steel Building (informal, historical) |
E695167
|
entity |
| Predicate | refersToOwner |
P44062
|
FINISHED |
| Object | Brookfield Properties |
—
|
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: Brookfield Properties | Statement: [U.S. Steel Building (informal, historical), refersToOwner, Brookfield Properties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToOwner Context triple: [U.S. Steel Building (informal, historical), refersToOwner, Brookfield Properties]
-
A.
targetOwner
chosen
Indicates that one entity is the owner or primary possessor of a specified target entity.
-
B.
refersToPrimaryUser
Indicates that something is referencing or pointing specifically to the main or primary user in the context.
-
C.
targetOwnership
Indicates that one entity holds ownership or proprietary control over the target entity.
-
D.
refersToRole
Indicates that one entity designates, mentions, or points to another entity specifically in its capacity as a role or position.
-
E.
typicallyOwnedBy
Indicates that something is most commonly or usually possessed or owned by a particular type of 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_69ef538608b081908b9f659bb09d5e0f |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 27, 2026, 1:29 p.m.