Triple
T32983084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyms Lane |
E843856
|
entity |
| Predicate | economicSignificanceFor |
P2313
|
FINISHED |
| Object | Crewe |
—
|
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: Crewe | Statement: [Pyms Lane, economicSignificanceFor, Crewe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: economicSignificanceFor Context triple: [Pyms Lane, economicSignificanceFor, Crewe]
-
A.
economicFunction
Indicates the role or purpose an entity serves within an economic system, such as how it contributes to production, distribution, or consumption of goods and services.
-
B.
economicSectorDominant
Indicates that one economic sector holds a leading or controlling position relative to others in terms of influence, output, or importance.
-
C.
economicSectorSourceOfWealth
Indicates that a particular economic sector is the primary source from which an entity derives its wealth or income.
-
D.
economicAspect
chosen
Indicates that something is related to, characterized by, or has implications for economic factors, conditions, or outcomes.
-
E.
economicDataSource
Indicates the source or origin from which economic data or statistics are obtained or derived.
- 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_69f3494c6f9c8190a255409fce8b1d3b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: May 1, 2026, 1:22 a.m.