Triple
T35423627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stockland shopping centre portfolio |
E1023860
|
entity |
| Predicate | tickerOfOwner |
P150250
|
FINISHED |
| Object | SGP |
—
|
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: SGP | Statement: [Stockland shopping centre portfolio, tickerOfOwner, SGP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tickerOfOwner Context triple: [Stockland shopping centre portfolio, tickerOfOwner, SGP]
-
A.
tickerFor
Indicates that one entity is the stock ticker symbol used to uniquely identify another entity (typically a publicly traded company or security) in financial markets.
-
B.
hasBrandOwnerTicker
chosen
Indicates that an entity is associated with the stock ticker symbol of the company that owns its brand.
-
C.
overseesTicker
Indicates that one entity has supervisory or managerial responsibility over the activities or status associated with a specific ticker symbol.
-
D.
associatedWithTicker
Indicates that an entity is linked or connected to a specific stock market ticker symbol.
-
E.
tickerSymbol
Indicates the association between a financial instrument or company and its unique abbreviated code used for trading on a securities exchange.
- 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7958ef49081909e4a8bfe3ef0d657 |
completed | May 3, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.