Triple
T4504056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sapsan |
E101288
|
entity |
| Predicate | additionalLanguageSupport |
P9103
|
FINISHED |
| Object | English (basic) |
—
|
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: English (basic) | Statement: [Sapsan, additionalLanguageSupport, English (basic)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: additionalLanguageSupport Context triple: [Sapsan, additionalLanguageSupport, English (basic)]
-
A.
languageProvision
Indicates that one entity supplies, supports, or makes available a particular language (or set of languages) for use by another entity.
-
B.
originalLanguageSupport
Indicates that one entity provides or maintains functionality, content, or interaction in the original language of another entity.
-
C.
additionalOfficialLanguage
Indicates that an entity has another language, beyond its primary one, that holds official or formally recognized status.
-
D.
hasSecondaryLanguage
chosen
Indicates that an entity possesses or uses a secondary language in addition to its primary language.
-
E.
hasLanguages
Indicates that an entity is associated with one or more languages it uses, supports, or is expressed in.
- 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_69bd43d175248190894dc58b5b395c26 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd56fca7d4819081deb34628e04f00 |
completed | March 20, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69bd521671688190bc655d25fa77eba2 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:01 p.m.