Triple
T17745926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Kopin |
E442988
|
entity |
| Predicate | governedTerritoryCharacteristic |
P128842
|
FINISHED |
| Object | remote |
—
|
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: remote | Statement: [Roman Kopin, governedTerritoryCharacteristic, remote]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedTerritoryCharacteristic Context triple: [Roman Kopin, governedTerritoryCharacteristic, remote]
-
A.
governedTerritory
Indicates that one entity exercises political authority or control over another entity or geographic area as its governing power.
-
B.
governsTerritoryType
Indicates that an authority or governing body exercises official control or administration over a specified type of territory.
-
C.
governedTerritoryVia
Indicates a relationship where an authority or governing body exercises control over a territory through an intermediary entity, mechanism, or arrangement.
-
D.
governingBodyTerritory
Indicates the territory or geographic area over which a governing body has authority or jurisdiction.
-
E.
governedIn
Indicates that one entity exercised governing authority or administrative control within a specified place or jurisdiction.
- 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47ad26940819090696c2cb86fd606 |
completed | April 19, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
| PDg | Predicate description generation | batch_69e3d37ab6988190bd326ea6f8dd4aaa |
completed | April 18, 2026, 6:54 p.m. |
Created at: April 10, 2026, 10:09 a.m.