Triple
T38598241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expo 83 |
E934139
|
entity |
| Predicate | locationCityStatus |
P22389
|
FINISHED |
| Object | major industrial and cultural center in Bulgaria |
—
|
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: major industrial and cultural center in Bulgaria | Statement: [Expo 83, locationCityStatus, major industrial and cultural center in Bulgaria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationCityStatus Context triple: [Expo 83, locationCityStatus, major industrial and cultural center in Bulgaria]
-
A.
cityStatusContext
chosen
Indicates the contextual status or role that a city holds within a broader administrative, political, or situational framework.
-
B.
cityLocation
Indicates that a city is geographically situated within or associated with a specific larger area or place.
-
C.
cityStatusAppliesTo
Indicates that a particular city status or designation is applicable to a given city or urban entity.
-
D.
impliesStatusOfCity
Indicates that one entity suggests, infers, or entails a particular status or condition of a city.
-
E.
cityRelocationStatus
Indicates the status or stage of a city’s relocation process from one place to another.
- 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.