Triple
T30833534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northwest street naming system of Washington, D.C. |
E785293
|
entity |
| Predicate | influencedByPlan |
P87217
|
FINISHED |
| Object | L’Enfant Plan |
—
|
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: L’Enfant Plan | Statement: [Northwest street naming system of Washington, D.C., influencedByPlan, L’Enfant Plan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: influencedByPlan Context triple: [Northwest street naming system of Washington, D.C., influencedByPlan, L’Enfant Plan]
-
A.
influencedIn
Indicates that one entity had an effect on or shaped another entity within a specific context, domain, or setting.
-
B.
influencedByCurrent
Indicates that something’s state, behavior, or outcome is affected or determined by the current conditions, context, or situation.
-
C.
decisionInfluencedBy
Indicates that a decision is shaped, guided, or affected by another factor, entity, or event.
-
D.
wereInfluencedBy
chosen
Indicates that one entity’s ideas, actions, or characteristics were shaped or affected by another entity.
-
E.
plannedVia
Indicates that something is arranged, organized, or scheduled by means of a particular method, process, or intermediary.
- 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_69f224b73d8c81908129383bfb397c87 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 29, 2026, 8:45 p.m.