Triple
T18651865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beetle Drive |
E455960
|
entity |
| Predicate | isInUpscaleArea |
P37114
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Beetle Drive, isInUpscaleArea, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInUpscaleArea Context triple: [Beetle Drive, isInUpscaleArea, true]
-
A.
isInUpscaleNeighborhood
chosen
Indicates that the subject is located within a neighborhood characterized by higher property values, amenities, and socioeconomic status compared to typical areas.
-
B.
isUpscale
Indicates that something possesses a high-end, luxurious, or premium quality or status compared to typical or standard options.
-
C.
isInArea
Indicates that one entity is located within the spatial bounds or region defined by another entity.
-
D.
isUrbanZoneFor
Indicates that a given area functions as an urban zone designated for a particular entity or purpose.
-
E.
isWithinMetroArea
Indicates that one location lies inside the geographic boundaries of a specified metropolitan area.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e55011a8208190acf5e6f69a441043 |
completed | April 19, 2026, 9:58 p.m. |
| PD | Predicate disambiguation | batch_69e478d85864819093cbad5ed9b54878 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:47 a.m.