Triple
T1642940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Street (Philadelphia) |
E35513
|
entity |
| Predicate | partOfPlan |
P29774
|
FINISHED |
| Object | original city plan of Philadelphia |
—
|
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: original city plan of Philadelphia | Statement: [High Street (Philadelphia), partOfPlan, original city plan of Philadelphia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfPlan Context triple: [High Street (Philadelphia), partOfPlan, original city plan of Philadelphia]
-
A.
plan
Indicates that an entity intends or arranges for a future action or sequence of actions to occur.
-
B.
bodyPlan
Indicates the overall structural organization and arrangement of an organism’s body, including the layout and relationship of its major parts.
-
C.
plannedUnder
Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
-
D.
planned
Indicates that an entity has intentionally arranged or scheduled another entity or event to occur in the future.
-
E.
planner
Indicates that an entity is responsible for organizing, scheduling, or coordinating activities, tasks, or resources.
- 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_69a88604618c81908b41f6429c431eb6 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a919306fd48190a245fc95e0e759d9 |
completed | March 5, 2026, 5:48 a.m. |
| PD | Predicate disambiguation | batch_69a907cc9d348190b76b0d3f596e5a81 |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a9192f975c8190bfd514a4b5a8786c |
completed | March 5, 2026, 5:48 a.m. |
Created at: March 4, 2026, 7:28 p.m.