Triple
T3850213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zelenogradsky Administrative Okrug |
E85276
|
entity |
| Predicate | hasOriginAs |
P3654
|
FINISHED |
| Object | planned center of Soviet electronics |
—
|
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: planned center of Soviet electronics | Statement: [Zelenogradsky Administrative Okrug, hasOriginAs, planned center of Soviet electronics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginAs Context triple: [Zelenogradsky Administrative Okrug, hasOriginAs, planned center of Soviet electronics]
-
A.
hasOriginIn
chosen
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
B.
hasOriginFeature
Indicates that an entity possesses a specific characteristic, attribute, or feature related to its origin or source.
-
C.
hasNameOrigin
Indicates that the origin or source of an entity’s name is specified by the related entity.
-
D.
classOrigin
Indicates the original class or category from which an entity is derived, instantiated, or classified.
-
E.
originallyBy
Indicates that one entity is the original creator, author, or source of another entity.
- 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_69aed936de1c81908f91bed80f70abb2 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeebcf67788190975105131baabc4b |
completed | March 9, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69aee750377c8190af70c79768c0edd8 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.