Triple
T14542964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AMP Capital |
E341215
|
entity |
| Predicate | managesAssetClass |
P77827
|
FINISHED |
| Object | listed real estate |
—
|
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: listed real estate | Statement: [AMP Capital, managesAssetClass, listed real estate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesAssetClass Context triple: [AMP Capital, managesAssetClass, listed real estate]
-
A.
overseesAssetClass
chosen
Indicates that one entity has responsibility for supervising, managing, or having authority over a particular asset class.
-
B.
coversAssetClass
Indicates that one entity (such as a product, service, or policy) includes, applies to, or provides coverage for a specified asset class.
-
C.
replicatesAssetClass
Indicates that one financial instrument or entity is designed to mirror or track the performance and characteristics of a specified asset class.
-
D.
mainAssetManaged
Indicates that one entity is responsible for managing another entity that serves as the primary or main asset.
-
E.
assetManagementFunction
Indicates the function or role responsible for overseeing, controlling, and optimizing the use and lifecycle of assets.
- 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_69d822db9c8481908213ceb39585f792 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb1be5a8081909bf727e28a5bba4a |
completed | April 14, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69de5c546c7081909e27d504ec360c5c |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:22 a.m.