Triple
T26819155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simon family |
E675198
|
entity |
| Predicate | businessHoldingsInclude |
P117057
|
FINISHED |
| Object | shopping malls |
—
|
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: shopping malls | Statement: [Simon family, businessHoldingsInclude, shopping malls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: businessHoldingsInclude Context triple: [Simon family, businessHoldingsInclude, shopping malls]
-
A.
businessHoldings
chosen
Indicates the relationship where one business owns, controls, or maintains financial or asset interests in another entity or set of entities.
-
B.
mediaHoldingsInclude
Indicates that a collection of media assets or rights contains or encompasses the specified media item(s).
-
C.
includesHoldingsFrom
Indicates that one entity’s set of holdings incorporates or contains the holdings originating from another entity.
-
D.
roleOfHolders
Indicates that certain entities serve as holders or bearers of a specified role, function, or position in relation to something else.
-
E.
portfolioHeldBy
Indicates that a particular portfolio is owned, managed, or maintained by a specified 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_69eee9b6b28481909332f83eb17e5170 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6383625cc8190aa223d8ef655743c |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 4:54 a.m.