Triple
T29844221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiraspol State University |
E757885
|
entity |
| Predicate | operatesPrimarilyFrom |
P93876
|
FINISHED |
| Object | Chișinău |
—
|
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: Chișinău | Statement: [Tiraspol State University, operatesPrimarilyFrom, Chișinău]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesPrimarilyFrom Context triple: [Tiraspol State University, operatesPrimarilyFrom, Chișinău]
-
A.
hasBaseOfOperations
Indicates that an entity uses a particular location as its primary place of operation or activity.
-
B.
operatedFrom
Indicates that an entity conducted its activities or operations starting from or based at a particular location or source.
-
C.
servesAsPrimaryAirportOperatorForCity
Indicates that an entity functions as the main organization responsible for operating the primary airport serving a particular city.
-
D.
isTypicallyBasedIn
chosen
Indicates that one entity is most commonly located, headquartered, or primarily operates within the context or place specified by another entity.
-
E.
hasOperatorHeadquartersIn
Indicates that the primary operational headquarters of an operator is located in a specified place.
- 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69ff38b960808190a8263348f1e5c0e4 |
completed | May 9, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69ff37d97d9c8190849b2bac14f9af1d |
completed | May 9, 2026, 1:34 p.m. |
Created at: April 29, 2026, 5:41 p.m.