Triple
T7586437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greenbelt Park |
E179622
|
entity |
| Predicate | isUrbanAdjacent |
P44123
|
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: [Greenbelt Park, isUrbanAdjacent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUrbanAdjacent Context triple: [Greenbelt Park, isUrbanAdjacent, true]
-
A.
isUrbanParkAdjacent
Indicates that an urban park is directly next to or shares a boundary with another specified area or feature.
-
B.
isUrbanNeighborhood
Indicates that a given area functions as a neighborhood located within an urban or city environment.
-
C.
isUrbanDistrict
Indicates that a given district is classified as an urban administrative or residential area rather than a rural one.
-
D.
hasUrbanProximity
chosen
Indicates that one entity is located near or within easy access to an urban area associated with another entity.
-
E.
isUrbanForm
Indicates that an entity represents or exhibits characteristics of an urban built environment or city-like spatial structure.
- 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_69c69f335248819093c1006f30513708 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9970efc8190b1b9286d86331359 |
completed | March 27, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e04c2c8190a889d928515d9b8e |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:52 p.m.