Triple
T3506706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vulcan Inc. |
E74092
|
entity |
| Predicate | assetClassManaged |
P28209
|
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: [Vulcan Inc., assetClassManaged, real estate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assetClassManaged Context triple: [Vulcan Inc., assetClassManaged, real estate]
-
A.
notableAssetClass
Indicates that an entity is significantly associated with, or recognized for, a particular class of assets.
-
B.
coversAssetClass
chosen
Indicates that one entity (such as a product, service, or policy) includes, applies to, or provides coverage for a specified asset class.
-
C.
assetType
Indicates the specific category or classification of an asset within a broader asset framework or system.
-
D.
isManagedFor
Indicates that one entity is administered, overseen, or controlled on behalf of another entity or purpose.
-
E.
managedIn
Indicates that one entity is administered, operated, or overseen within the scope, control, or jurisdiction of another entity.
- 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_69ad85ce7a9c81909ddc5cf0cb67a6e3 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbf52bd8819085a2ac5f48cc5c68 |
completed | March 8, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69adae0e770481908528fa35eda53003 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.