Triple
T7337917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moore neighborhood |
E169176
|
entity |
| Predicate | neighborhoodRadius |
P77122
|
FINISHED |
| Object | 1 (for the standard Moore neighborhood) |
—
|
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: 1 (for the standard Moore neighborhood) | Statement: [Moore neighborhood, neighborhoodRadius, 1 (for the standard Moore neighborhood)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neighborhoodRadius Context triple: [Moore neighborhood, neighborhoodRadius, 1 (for the standard Moore neighborhood)]
-
A.
neighborhoodSize
Indicates the size or extent of the surrounding area or local vicinity associated with an entity.
-
B.
runsThroughNeighborhood
Indicates that something (such as a route, path, or service) passes through or traverses a particular neighborhood.
-
C.
approximateRadius
Indicates that one entity specifies or provides an estimated value for the radius of another entity.
-
D.
neighborhood
Indicates that one entity is located in close spatial proximity to another, typically within the same local area or district.
-
E.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
- F. None of above. chosen
Provenance (4 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_69c68a57710481909f0c1f3c6ebdb6f2 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f347f25081908e6086d4073295f5 |
completed | March 27, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c6f028fd748190b2ea5c3081958a42 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f3463d0481908aed9ed43a8ac6a8 |
completed | March 27, 2026, 9:14 p.m. |
Created at: March 27, 2026, 3:04 p.m.