Triple
T26005766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gopcevich family |
E646751
|
entity |
| Predicate | geographicSphereOfActivity |
P65106
|
FINISHED |
| Object | Central Europe |
—
|
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: Central Europe | Statement: [Gopcevich family, geographicSphereOfActivity, Central Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicSphereOfActivity Context triple: [Gopcevich family, geographicSphereOfActivity, Central Europe]
-
A.
area of activity
Indicates the domain, field, or sphere in which an entity is active or carries out its primary functions or operations.
-
B.
geographicAreaOfSupport
Indicates the geographic region or area within which support, assistance, or services are provided or applicable.
-
C.
регионДеятельности
chosen
Indicates the geographic region or area in which an entity carries out its activities or operations.
-
D.
strategicAreaServed
Indicates that an entity provides services or exerts influence within a particular area considered strategically important.
-
E.
sphereOfInfluence
Indicates the area or domain within which an entity exerts significant control, impact, or authority over others.
- 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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 22, 2026, 9 a.m.