Triple
T15636952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PKT Gdynia |
E375969
|
entity |
| Predicate | networkTypeOperated |
P3937
|
FINISHED |
| Object | trolleybus network |
—
|
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: trolleybus network | Statement: [PKT Gdynia, networkTypeOperated, trolleybus network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkTypeOperated Context triple: [PKT Gdynia, networkTypeOperated, trolleybus network]
-
A.
networkType
chosen
Indicates the category or kind of network associated with or used by an entity (e.g., wired, wireless, virtual, or specific protocol-based networks).
-
B.
operatesNetwork
Indicates that an entity manages, controls, or runs the functioning of a network.
-
C.
operatedInNetwork
Indicates that an entity carried out its activities or services within a specified network or system.
-
D.
wirelessOperator
Indicates that an entity operates, manages, or provides services for a wireless communication system or network for another entity.
-
E.
networkTypePromoted
Indicates that a particular type of network has been elevated, highlighted, or given priority status within a system or context.
- 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04eba51f08190ac5d9de7fc89405a |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda868d4481908f4bce1c64d2902a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:14 a.m.