Triple
T16299548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North 12th Street (Philadelphia) |
E395746
|
entity |
| Predicate | hasNumberedStreetSystem |
P49387
|
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: [North 12th Street (Philadelphia), hasNumberedStreetSystem, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberedStreetSystem Context triple: [North 12th Street (Philadelphia), hasNumberedStreetSystem, true]
-
A.
hasStreetNumberingSystem
chosen
Indicates that a location or area uses an organized system for assigning numbers to buildings or addresses along its streets.
-
B.
hasRoadNumberSystem
Indicates that a place or region uses a specific system for assigning numbers to its roads or highways.
-
C.
isNumberedStreet
Indicates that a street is designated primarily by a number (e.g., "1st Street," "42nd Avenue") rather than by a proper name.
-
D.
hasNumberOfStreets
Indicates the relationship that specifies how many streets are associated with or contained within a given entity.
-
E.
hasJunctionNumbering
Indicates that a road or route is assigned a specific numbering system for its junctions or intersections.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e31c9e8819094593f3aeb44f2ca |
completed | April 17, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.