Triple
T28597780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shape Properties |
E723820
|
entity |
| Predicate | hasTypeOfAsset |
P15055
|
FINISHED |
| Object | income-producing properties |
—
|
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: income-producing properties | Statement: [Shape Properties, hasTypeOfAsset, income-producing properties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfAsset Context triple: [Shape Properties, hasTypeOfAsset, income-producing properties]
-
A.
hasKeyAssetType
Indicates that an entity possesses or is associated with a specific type or category of key (primary or critical) asset.
-
B.
ownsAssetType
Indicates that an entity possesses ownership rights over an asset of a specified type.
-
C.
assetType
chosen
Indicates the specific category or classification of an asset within a broader asset framework or system.
-
D.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
E.
governsAssetType
Indicates that one entity has authority or control over the rules, usage, or management of a particular type or class of asset.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: April 28, 2026, 4:22 a.m.