Triple
T4707577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 47th Street Diamond District |
E104427
|
entity |
| Predicate | approximateBlockLength |
P59093
|
FINISHED |
| Object | one city block |
—
|
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: one city block | Statement: [47th Street Diamond District, approximateBlockLength, one city block]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateBlockLength Context triple: [47th Street Diamond District, approximateBlockLength, one city block]
-
A.
estimatedNumberOfBlocks
Indicates the approximate count of discrete blocks associated with or involved in the given entity or context.
-
B.
approximateLengthInMeters
Indicates the estimated or roughly measured length of something expressed in meters.
-
C.
blockSize
Indicates the size or capacity of a discrete block unit within a larger structure or system.
-
D.
approximateSize
Indicates that one entity has a size that is roughly or approximately equal to the size of another entity.
-
E.
approximateCapacity
Indicates that one entity has an estimated or rough capacity value relative to another or to a specified measure.
- 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_69bd43eac3c08190af7e4020c6c3704c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd680beb508190b3d74e20e1c64405 |
completed | March 20, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69bd621ddcd88190903288566f5e5dab |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd680b06e881908de87edf815f3cc0 |
completed | March 20, 2026, 3:30 p.m. |
Created at: March 20, 2026, 1:17 p.m.