Triple
T24781074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Лаперу́зов пролив |
E619996
|
entity |
| Predicate | такжеИзвестенКак |
P39
|
FINISHED |
| Object | пролив Лаперуза |
—
|
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: пролив Лаперуза | Statement: [Лаперу́зов пролив, такжеИзвестенКак, пролив Лаперуза]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: такжеИзвестенКак Context triple: [Лаперу́зов пролив, такжеИзвестенКак, пролив Лаперуза]
-
A.
alsoKnownAs
chosen
Indicates that one entity is an alternative name, alias, or designation for another entity.
-
B.
известенКак
Indicates that one entity is known or recognized by a particular name, title, or role.
-
C.
knownAsBy
Indicates that one entity is referred to or recognized by another entity using a particular name or designation.
-
D.
alsoKnownThrough
Indicates that an entity is recognized or identified by means of another entity, such as a source, context, or intermediary, through which its alternative name or identity is known.
-
E.
isWidelyKnownAs
Indicates that an entity is commonly referred to or recognized by a particular name or label by a broad audience.
- 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410d67a208190909034a085b20b59 |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:44 a.m.