Triple
T8848164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Клушино |
E210561
|
entity |
| Predicate | известноКак |
P84972
|
FINISHED |
| Object | место рождения Юрия Гагарина |
—
|
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: место рождения Юрия Гагарина | Statement: [Клушино, известноКак, место рождения Юрия Гагарина]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: известноКак Context triple: [Клушино, известноКак, место рождения Юрия Гагарина]
-
A.
knownIn
Indicates that an entity is recognized, acknowledged, or familiar within a particular context, domain, or group.
-
B.
knows
Indicates that one entity has knowledge or awareness of another entity or piece of information.
-
C.
knownFrom
Indicates that one entity is aware of, has learned about, or recognizes another entity through a specified source, context, or medium.
-
D.
isWidelyKnown
Indicates that something is generally recognized or familiar to a large number of people.
-
E.
knownResult
Indicates that the outcome or consequence of an action, process, or event is already determined and available.
- F. None of above. chosen
Provenance (4 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_69ca838967bc8190b46c3c80a2887ea4 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60aa6db0819097c3257499200afc |
completed | April 1, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69cc5c25b874819084c9ba391703e066 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cff3608819081d2d7e5c16d44b7 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:49 p.m.