Triple
T4756210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RZD International |
E105593
|
entity |
| Predicate | usesStandards |
P1587
|
FINISHED |
| Object | international railway standards |
—
|
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: international railway standards | Statement: [RZD International, usesStandards, international railway standards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesStandards Context triple: [RZD International, usesStandards, international railway standards]
-
A.
usesStandard
chosen
Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
-
B.
isStandardOf
Indicates that something serves as the recognized norm, reference, or benchmark by which another thing is defined, measured, or evaluated.
-
C.
isStandard
Indicates that something conforms to an established norm, specification, or commonly accepted rule.
-
D.
includesStandard
Indicates that one entity contains, incorporates, or makes use of a particular standard as part of its definition, implementation, or specification.
-
E.
standardsType
Indicates the classification or category of standards that apply to or are associated with an entity or activity.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64e9d80c819088532921a46ea1d6 |
completed | March 20, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69bd6223defc8190823665a6592c1154 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.