Triple
T22929244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Jersey municipal street systems |
E569388
|
entity |
| Predicate | designGuidedBy |
P23439
|
FINISHED |
| Object | local master plans |
—
|
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: local master plans | Statement: [New Jersey municipal street systems, designGuidedBy, local master plans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designGuidedBy Context triple: [New Jersey municipal street systems, designGuidedBy, local master plans]
-
A.
designedBy
Indicates that one entity is the creator, planner, or architect responsible for the form or structure of another entity.
-
B.
designLead
Indicates that one entity serves as the primary designer or person in charge of leading the design work for another entity or project.
-
C.
designedWith
chosen
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
-
D.
designSucceededBy
Indicates that one design is followed or replaced by another design in a temporal or version sequence.
-
E.
designSpecifiedBy
Indicates that the design or specification of one entity is defined, authored, or determined by another entity.
- 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_69e2458f7d008190901dccbaebeaba24 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f180dc33e8819099e5ad87207de57f |
completed | April 29, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:44 p.m.