Triple
T34962673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Могилёв-Подольский |
E1008301
|
entity |
| Predicate | имеетАвтомобильноеСообщениеС |
P182463
|
FINISHED |
| Object | Кишинёв |
—
|
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: Кишинёв | Statement: [Могилёв-Подольский, имеетАвтомобильноеСообщениеС, Кишинёв]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: имеетАвтомобильноеСообщениеС Context triple: [Могилёв-Подольский, имеетАвтомобильноеСообщениеС, Кишинёв]
-
A.
utilityInvolved
Indicates that a utility service or provider is involved in, associated with, or plays a role in the referenced situation or relationship.
-
B.
hasNotableVehicleAssociated
Indicates that an entity is associated with a specific vehicle that is considered notable or significant in some recognized context.
-
C.
hasVehicle
Indicates that one entity possesses, owns, or is assigned a vehicle.
-
D.
hasVehicularUse
Indicates that something is used for, intended for, or associated with operation by vehicles or vehicular traffic.
-
E.
vehiclePolicy
Indicates a relationship where a policy governs, regulates, or defines rules and conditions for the use, operation, or management of a vehicle.
- 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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78dbf72648190a4971a558e9d1889 |
completed | May 3, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78ce43094819093857fc99f269afe |
completed | May 3, 2026, 5:59 p.m. |
Created at: May 3, 2026, 4 p.m.