Triple
T24814066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 745 |
E620866
|
entity |
| Predicate | leasingCompany |
P10974
|
FINISHED |
| Object | Rock Rail |
—
|
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: Rock Rail | Statement: [British Rail Class 745, leasingCompany, Rock Rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leasingCompany Context triple: [British Rail Class 745, leasingCompany, Rock Rail]
-
A.
leaseOrigin
Indicates that one entity is the original source or starting point from which a lease agreement or leasing arrangement is derived.
-
B.
leaseRecipient
chosen
Indicates the party that receives or holds rights to use a property or asset under a lease agreement from another party.
-
C.
ownerStudio
Indicates that a studio is the owner or primary producing entity responsible for a given work or asset.
-
D.
leaseAgreement
Indicates a contractual relationship in which one party grants another the right to use an asset or property for a specified period in exchange for agreed payments or conditions.
-
E.
leaseMechanism
Indicates a relationship where one party grants another the right to use an asset or property under specified lease terms and conditions.
- 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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:59 a.m.