Triple
T5502054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freight Operating Companies |
E144350
|
entity |
| Predicate | mayOwnOrLease |
P27908
|
FINISHED |
| Object | rolling stock |
—
|
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: rolling stock | Statement: [Freight Operating Companies, mayOwnOrLease, rolling stock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayOwnOrLease Context triple: [Freight Operating Companies, mayOwnOrLease, rolling stock]
-
A.
ownsOrLeases
chosen
Indicates that one entity has legal rights to use or control another entity either through ownership or through a lease agreement.
-
B.
ownerOccupation
Indicates that the occupation or job role of an entity that owns something is being specified or described.
-
C.
canOwn
Indicates that one entity is permitted or legally able to possess or hold ownership rights over another entity.
-
D.
ownsPropertyIn
Indicates that one entity possesses legal ownership rights over property located within a specified place or jurisdiction.
-
E.
ownershipType
Indicates the specific nature or category of the ownership relationship that one entity holds over another.
- 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_69c008f5a2748190bce7a39aabf87a6d |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f0a512c81908f077378917e5879 |
completed | March 22, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69c01b052f3c81909f71c6add0f35a6f |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:32 p.m.