Triple
T28193955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR Co., Ltd. |
E716387
|
entity |
| Predicate | operatesInNetwork |
P65111
|
FINISHED |
| Object | Korea Train Express 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: Korea Train Express network | Statement: [SR Co., Ltd., operatesInNetwork, Korea Train Express network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesInNetwork Context triple: [SR Co., Ltd., operatesInNetwork, Korea Train Express network]
-
A.
operatesNetwork
Indicates that an entity manages, controls, or runs the functioning of a network.
-
B.
operatedInNetwork
chosen
Indicates that an entity carried out its activities or services within a specified network or system.
-
C.
operatesNetworkFeature
Indicates that an entity is responsible for running or managing a particular network feature or function.
-
D.
operatedAsNetworkOf
Indicates that an entity functioned or was utilized as a coordinated network of interconnected components, units, or organizations.
-
E.
isPartOfNetworkServing
Indicates that one entity functions as a component within, or is supported by, a particular network that provides services to it or through it.
- 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_69efd6b612f48190a72012b520afbd10 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fe7bfc94bc81909eeec946e8c1c450 |
completed | May 9, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69fe7b74a1188190886f128e07f712da |
completed | May 9, 2026, 12:10 a.m. |
Created at: April 27, 2026, 10:26 p.m.