Triple
T1338984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Western Railway |
E28420
|
entity |
| Predicate | operatesFranchise |
P3695
|
FINISHED |
| Object | Great Western franchise |
—
|
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: Great Western franchise | Statement: [Great Western Railway, operatesFranchise, Great Western franchise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesFranchise Context triple: [Great Western Railway, operatesFranchise, Great Western franchise]
-
A.
distributesFranchise
Indicates that one party grants or allocates franchise rights or opportunities to another party.
-
B.
operatesBy
Indicates that an entity performs its function, action, or process through the use or application of another entity (e.g., a method, mechanism, or principle).
-
C.
franchiseStatus
Indicates the current standing or condition of a franchise relationship between parties, such as whether it is active, inactive, pending, or terminated.
-
D.
operatesOver
chosen
Indicates that one entity performs actions or exerts functional control across, upon, or throughout another entity or domain.
-
E.
franchiseOf
Indicates that one entity operates as a franchise belonging to or licensed by another entity.
- 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_69a49854eb3481908c7d56b2e449a290 |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c21303c881908fef0b32831222fe |
completed | March 1, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69a4bef174708190a07bbc697fe19a2d |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.