Triple
T21261590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ridge Avenue |
E524015
|
entity |
| Predicate | isDiagonalTo |
P130287
|
FINISHED |
| Object | Philadelphia street grid |
—
|
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: Philadelphia street grid | Statement: [Ridge Avenue, isDiagonalTo, Philadelphia street grid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDiagonalTo Context triple: [Ridge Avenue, isDiagonalTo, Philadelphia street grid]
-
A.
runsDiagonally
chosen
Indicates that one entity extends or moves in a diagonal direction relative to another reference frame or axis.
-
B.
isInDirectionOf
Indicates that one entity is oriented or positioned toward the direction in which another entity lies.
-
C.
diagonalProperty
Indicates a relationship where something possesses or exhibits a diagonal characteristic, alignment, or behavior relative to a reference frame or structure.
-
D.
hasOppositeDirectionTo
Indicates that one entity’s direction is exactly reversed or opposed to the direction of another entity.
-
E.
diagonalCount
Indicates the number of diagonals associated with or present in a given object, structure, or configuration.
- 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_69e0b5156d7881909bd4f83676590715 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735e899e081909d3c98fb12a8b476 |
completed | April 21, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:59 p.m.