Triple
T5093755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westbury neighborhood |
E114816
|
entity |
| Predicate | treeCoverage |
P29206
|
FINISHED |
| Object | mature trees |
—
|
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: mature trees | Statement: [Westbury neighborhood, treeCoverage, mature trees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treeCoverage Context triple: [Westbury neighborhood, treeCoverage, mature trees]
-
A.
branchCoverage
Indicates that one entity measures or represents how many decision branches in another entity’s control flow have been executed during testing.
-
B.
forestCoverCharacteristic
chosen
Indicates a relationship where a forested area possesses a specific attribute or quality related to its tree or vegetation cover.
-
C.
regionCoverage
Indicates that one entity geographically spans, includes, or serves the area defined by another entity.
-
D.
altitudeCoverageCharacteristic
Indicates the range or specific values of altitude over which something (such as a system, sensor, or service) is designed to operate or provide coverage.
-
E.
formatCoverage
Indicates how thoroughly or extensively a particular format or formatting scheme is applied or supported in a given context.
- 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_69bd443fc49c819089629c00e311310c |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75454920819086e09d6055087e40 |
completed | March 20, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69bd715c0a448190afc837c6c31dc6ab |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:40 p.m.