Triple
T34018791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chocim |
E872321
|
entity |
| Predicate | historicalNameInRomanian |
P23117
|
FINISHED |
| Object | Hotin |
—
|
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: Hotin | Statement: [Chocim, historicalNameInRomanian, Hotin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalNameInRomanian Context triple: [Chocim, historicalNameInRomanian, Hotin]
-
A.
historicalNameInLatin
Indicates that an entity has a historically used name expressed in Latin.
-
B.
historicalNameGivenBy
Indicates that one entity is the name historically assigned to another entity by a specific source, culture, or period.
-
C.
historicalNameInEnglish
Indicates that an entity is associated with a historical English-language name by which it was known in the past.
-
D.
nameInRomanian
chosen
Indicates that one entity is the Romanian-language name or designation of another entity.
-
E.
historicalNameType
Indicates that the relationship specifies the type or category of a historical name associated with an 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_69f349a19ad88190ab586f010c804a8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a00372ff0e48190b3ed91f9bae9da6c |
completed | May 10, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_6a00359c1b8481909c1e43df9f5a789a |
completed | May 10, 2026, 7:37 a.m. |
Created at: May 1, 2026, 1:51 a.m.