Triple
T29145825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Webster’s Corners |
E738768
|
entity |
| Predicate | typicalDensity |
P202542
|
FINISHED |
| Object | low-density residential |
—
|
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: low-density residential | Statement: [Webster’s Corners, typicalDensity, low-density residential]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDensity Context triple: [Webster’s Corners, typicalDensity, low-density residential]
-
A.
typeOfDensity
Indicates the specific category or kind of density (e.g., mass, population, charge) that characterizes a given quantity or measurement.
-
B.
typicalPopulationDensity
chosen
Indicates the usual or characteristic number of individuals per unit area associated with an entity or region.
-
C.
typicalUnionDensity
Indicates the usual or characteristic level of labor union membership or representation within a given group, sector, or region.
-
D.
hasMeanDensity
Indicates that one entity possesses a specified average mass per unit volume (mean density).
-
E.
givesDensityOf
Indicates that one entity provides or specifies the density value 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_6a01839b071481909f9cc79a6a09387d |
completed | May 11, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_6a017edbed688190baa61cbae5110c8e |
completed | May 11, 2026, 7:01 a.m. |
Created at: April 28, 2026, 11:39 a.m.