Triple
T14386489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grass River Property |
E356735
|
entity |
| Predicate | propertyTypeFocus |
P68889
|
FINISHED |
| Object | retail 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: retail properties | Statement: [Grass River Property, propertyTypeFocus, retail properties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propertyTypeFocus Context triple: [Grass River Property, propertyTypeFocus, retail properties]
-
A.
propertyTypeOwned
Indicates that one entity owns a specific type or category of property in relation to another entity.
-
B.
propertyType_rtx
chosen
Indicates that one entity has a specific type or category of property in relation to another entity.
-
C.
propertyType_rid
Indicates that an entity is associated with a specific property type identified by a unique resource identifier (RID).
-
D.
residenceType
Indicates the kind or category of dwelling or living arrangement associated with an entity.
-
E.
propertyTypeMix
Indicates that an entity involves or consists of a combination of different types of properties rather than a single uniform property type.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9025cff881908c08224d90d9f750 |
completed | April 14, 2026, 7:06 p.m. |
| PD | Predicate disambiguation | batch_69de2aa024c48190805df6a9d63deb10 |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:16 a.m.