Triple
T10905589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metrolink fare zones |
E257559
|
entity |
| Predicate | relatedSystem |
P37
|
FINISHED |
| Object | Bee Network |
E52496
|
NE 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: Bee Network | Statement: [Metrolink fare zones, relatedSystem, Bee Network]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bee Network Context triple: [Metrolink fare zones, relatedSystem, Bee Network]
-
A.
Bee Network
chosen
Bee Network is Greater Manchester’s integrated public transport system brand, unifying buses, trams, cycling and walking under a single, coordinated network.
-
B.
the Bee
The Bee is a former name meaning associated with the genus Musca, historically used to denote a bee-like characteristic or identity.
-
C.
Aurora Network
Aurora Network is a European university alliance focused on collaboration in research, education, and innovation among its member institutions.
-
D.
Emerald Network
The Emerald Network is a pan-European ecological network of protected areas aimed at conserving habitats and species of special importance under the Bern Convention.
-
E.
BEE
BEE is the ICAO airline designator used to identify Flybe in international aviation operations.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770656c288190828e71600bb0acd4 |
completed | April 9, 2026, 9:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e155454890819087028a72ac2be8de |
completed | April 16, 2026, 9:31 p.m. |
Created at: April 8, 2026, 9:22 p.m.