Triple
T9530313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RusLine |
E229872
|
entity |
| Predicate | hasLogoText |
P3623
|
FINISHED |
| Object | RusLine |
E229872
|
NE 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: RusLine | Statement: [RusLine, hasLogoText, RusLine]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RusLine Context triple: [RusLine, hasLogoText, RusLine]
-
A.
RusLine
chosen
RusLine is a Russian regional airline that operates domestic and short-haul international flights, primarily using a fleet of regional jets.
-
B.
RUSLINE AIR
RUSLINE AIR is the radio callsign used by RusLine, a Russian regional airline operating domestic and short-haul international flights.
-
C.
Transsib
Transsib is a common abbreviation for the Trans-Siberian Railway, the vast rail line that spans Russia from Moscow to the Pacific Ocean.
-
D.
Filevskaya Line
Filevskaya Line is one of the lines of the Moscow Metro, known for its partially surface-level sections and service to western districts of the city.
-
E.
Amur–Yakutsk Mainline
The Amur–Yakutsk Mainline is a major Russian railway line in the Russian Far East that extends the Trans-Siberian Railway northward toward Yakutsk, improving access to the remote Sakha Republic.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca8479934c81908006d0e6e970ae05 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98b2de3081909be70d9ab187dce6 |
completed | April 1, 2026, 10:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1527253588190ac365203ef382a2d |
completed | April 4, 2026, 6:03 p.m. |
Created at: March 30, 2026, 8 p.m.