Triple
T34620910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LMS 45407 |
E888998
|
entity |
| Predicate | mainlineUse |
P13668
|
FINISHED |
| Object | mainline charter operations |
—
|
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: mainline charter operations | Statement: [LMS 45407, mainlineUse, mainline charter operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainlineUse Context triple: [LMS 45407, mainlineUse, mainline charter operations]
-
A.
mainLine
Indicates that something serves as the primary or central line, route, or sequence among a set of related lines.
-
B.
mainUseContinued
Indicates that the primary use or function of something persists or remains in effect over a subsequent period.
-
C.
majorUse
chosen
Indicates that something serves as the primary or most significant use or application of an entity.
-
D.
mainlyUses
Indicates that one entity primarily relies on, employs, or utilizes another entity as its main tool, method, resource, or medium.
-
E.
servesMainLine
Indicates that one entity functions as the primary or main service line for 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_69f349d584e08190b40b9f6281ad50c4 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:04 a.m.