Triple
T31019965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inland Securities Corporation |
E790427
|
entity |
| Predicate | marketsProductsFor |
P63582
|
FINISHED |
| Object | Inland Real Estate Group |
—
|
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: Inland Real Estate Group | Statement: [Inland Securities Corporation, marketsProductsFor, Inland Real Estate Group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketsProductsFor Context triple: [Inland Securities Corporation, marketsProductsFor, Inland Real Estate Group]
-
A.
marketedProducts
Indicates that an entity promotes, sells, or otherwise brings specific products to market.
-
B.
productFor
Indicates that one entity is intended to be used by, with, or in relation to another entity as its product or offering.
-
C.
marketsThrough
chosen
Indicates that one entity promotes, sells, or distributes its products or services by using another entity as a marketing or sales channel.
-
D.
productsTraded
Indicates that one entity exchanges or deals specific goods or commodities with another entity.
-
E.
productWith
Indicates a relationship where one entity is associated with, contains, or is offered together with another entity as a product.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 29, 2026, 8:58 p.m.