Triple
T12601635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Real Estate and Infrastructure Investments |
E300870
|
entity |
| Predicate | portfolioScope |
P12124
|
FINISHED |
| Object | global |
—
|
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: global | Statement: [Real Estate and Infrastructure Investments, portfolioScope, global]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portfolioScope Context triple: [Real Estate and Infrastructure Investments, portfolioScope, global]
-
A.
scopeOfProducts
Indicates the range or extent of products that fall under a particular category, responsibility, or context.
-
B.
portfolioOf
chosen
Indicates that one entity is the collection of investments, works, or assets that are owned, managed, or represented by another entity.
-
C.
productionScope
Indicates the extent or boundaries of what is included in a given production activity or process.
-
D.
workCatalogueScope
Indicates that a work is included within the defined scope or coverage of a particular catalogue.
-
E.
scopeOfContribution
Indicates the specific area, domain, or extent within which an entity’s contribution or involvement applies.
- 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9559458dc8190bc4d6e697e99d70e |
completed | April 10, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69d9541894fc8190a0c3706a414279f0 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:09 p.m.