Triple
T35752289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baku City Circuit |
E1033348
|
entity |
| Predicate | DRSZones |
P30566
|
FINISHED |
| Object | multiple |
—
|
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: multiple | Statement: [Baku City Circuit, DRSZones, multiple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DRSZones Context triple: [Baku City Circuit, DRSZones, multiple]
-
A.
hasDRSZones
chosen
Indicates that one entity possesses, defines, or is associated with specific DRS (Disaster Recovery Site or similarly defined) zones.
-
B.
coreZoneArea
Indicates the area or spatial extent of a designated core zone within a larger region or system.
-
C.
numberOfZones
Indicates the quantity of distinct zones associated with or contained by a given entity.
-
D.
zoneDesign
Indicates a relationship where an entity defines, specifies, or configures the design or layout of a particular zone or area.
-
E.
dispersalZoneFor
Indicates the area or region designated for the spreading, distribution, or release of a specified 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a197aee48190bbd69f670a3f7721 |
completed | May 3, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.