Triple
T35049492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bologovsky District |
E1011288
|
entity |
| Predicate | hasImportantTransportRole |
P36293
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Bologovsky District, hasImportantTransportRole, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImportantTransportRole Context triple: [Bologovsky District, hasImportantTransportRole, yes]
-
A.
hasMajorTransportationRole
chosen
Indicates that an entity plays a primary or significant role in providing or supporting transportation services or infrastructure.
-
B.
hasPublicTransitRole
Indicates that an entity holds a specific functional role or responsibility within a public transit system.
-
C.
transportationRole
Indicates a role or function that an entity has specifically in the context of providing, operating, or supporting transportation.
-
D.
isMajorTransportLink
Indicates that something serves as a primary or highly significant route or connection for transporting people or goods between places.
-
E.
hasTransportSignificance
Indicates that something plays an important role or has notable relevance within a transportation or transit context.
- 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:01 p.m.