Triple
T24932263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M>Train |
E623218
|
entity |
| Predicate | operatedUnderBranding |
P27763
|
FINISHED |
| Object | M>Train |
—
|
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: M>Train | Statement: [M>Train, operatedUnderBranding, M>Train]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedUnderBranding Context triple: [M>Train, operatedUnderBranding, M>Train]
-
A.
operatedByBrand
Indicates that an entity (such as a service, location, or product line) is run, managed, or controlled by a particular brand.
-
B.
operatesUnderName
Indicates that an entity conducts its activities or business using a particular name, which may differ from its official or legal name.
-
C.
hasBranding
Indicates that one entity carries, displays, or is associated with the brand identity of another entity.
-
D.
hasUnderlyingCompanyBrand
chosen
Indicates that one entity is associated with or operates under the corporate brand of another company as its underlying brand.
-
E.
operatedAs
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
- 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_69e2fac6b5a48190a1c38857f00915a9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 18, 2026, 5:30 a.m.