Triple
T7875715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhaetian Railway |
E182845
|
entity |
| Predicate | alsoOperatesInLanguage |
P18404
|
FINISHED |
| Object | Romansh |
—
|
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: Romansh | Statement: [Rhaetian Railway, alsoOperatesInLanguage, Romansh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoOperatesInLanguage Context triple: [Rhaetian Railway, alsoOperatesInLanguage, Romansh]
-
A.
hasPrimaryLanguageOfOperations
Indicates that an entity conducts its main activities or operations primarily using a specified language.
-
B.
usesWorkingLanguagesOf
Indicates that one entity employs or operates using the working languages associated with another entity.
-
C.
tertiaryLanguageOfOperation
Indicates that an entity uses a specified language as its third most prominent or prioritized language of operation.
-
D.
isWorkingLanguageOf
chosen
Indicates that a particular language is officially used as a medium of work, communication, or operation within a specified organization, institution, or context.
-
E.
alsoInLanguageRegion
Indicates that two or more entities are located within or associated with the same language-defined geographic region.
- 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_69ca828a17248190b46defe758bc5ad3 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39aa7ca88190b88a18f6a8971e51 |
completed | March 31, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69cae928e1b88190b0620f4c4f03bc7d |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:57 p.m.