Triple
T10192960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Lane station |
E238082
|
entity |
| Predicate | hasMapDesignation |
P19168
|
FINISHED |
| Object | SEPTA Regional Rail map |
—
|
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: SEPTA Regional Rail map | Statement: [Queen Lane station, hasMapDesignation, SEPTA Regional Rail map]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMapDesignation Context triple: [Queen Lane station, hasMapDesignation, SEPTA Regional Rail map]
-
A.
mapDesignation
chosen
Indicates a formal label or identifier that is assigned to something specifically for use on a map.
-
B.
hasRegionDesignation
Indicates that an entity is assigned or associated with a specific regional classification or designation.
-
C.
hasCityDesignatedAs
Indicates that an entity has a specific city formally assigned or designated to it in a particular role or capacity.
-
D.
hasCriticalDesignation
Indicates that an entity has been assigned a status or label marking it as critical in importance, priority, or required attention.
-
E.
hasDiscoveryDesignation
Indicates that an entity has been assigned a specific designation or label associated with its discovery.
- 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_69ca84de1b208190bf17bb305b002605 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdedc675008190b8248325f5a208bf |
completed | April 2, 2026, 4:17 a.m. |
| PD | Predicate disambiguation | batch_69cd7c8477648190bc55c56aeec507d3 |
completed | April 1, 2026, 8:13 p.m. |
Created at: March 30, 2026, 9:13 p.m.