Triple
T28753631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riverton, New Jersey |
E731602
|
entity |
| Predicate | isHistoricSuburbOf |
P165283
|
FINISHED |
| Object | Philadelphia, Pennsylvania |
—
|
NE NERFINISHED |
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, Pennsylvania | Statement: [Riverton, New Jersey, isHistoricSuburbOf, Philadelphia, Pennsylvania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHistoricSuburbOf Context triple: [Riverton, New Jersey, isHistoricSuburbOf, Philadelphia, Pennsylvania]
-
A.
isResidentialSuburbOf
Indicates that one area is a residential suburb that is part of or lies within the urban region of another area.
-
B.
isCommercialSuburbOf
Indicates that one area functions primarily as a business or commercial district that is part of, or subordinate to, a larger urban area or city.
-
C.
isOuterSuburbOf
Indicates that one place is a suburban area located on the outer edge or periphery of another, typically larger, urban area.
-
D.
isEasternSuburbOf
Indicates that one place is a suburb located to the east of another place.
-
E.
innerSuburbOf
Indicates that one location is a suburb situated within or forming part of a larger city or metropolitan area.
- 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_69f043ed68a881909e858a06bab7a247 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f657f914fc819096cdb3664e962042 |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f651ada6048190a7b4a6981565dc3a |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 28, 2026, 6:08 a.m.