Triple
T7002769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crown Property Bureau |
E162376
|
entity |
| Predicate | typeOfAssetsManaged |
P29377
|
FINISHED |
| Object | 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: real estate | Statement: [Crown Property Bureau, typeOfAssetsManaged, real estate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAssetsManaged Context triple: [Crown Property Bureau, typeOfAssetsManaged, real estate]
-
A.
managesWealthFor
Indicates that one entity is responsible for overseeing, controlling, or administering the financial assets or wealth of another entity.
-
B.
typeOfHedgeFund
Indicates that one entity is a specific category or kind of hedge fund in relation to another entity.
-
C.
typicalHoldingsType
Indicates the usual or most common category of holdings associated with an entity or account.
-
D.
eraOfMajorHoldings
Indicates the historical time period during which the primary or most significant holdings associated with an entity were established or predominant.
-
E.
notableAssetClass
chosen
Indicates that an entity is significantly associated with, or recognized for, a particular class 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_69c6885928148190ae31909fbb5e9849 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dc1115c48190a9363473ae21b6c1 |
completed | March 27, 2026, 7:35 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c67c94819084fdcf0398606027 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:33 p.m.