Triple
T31141741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MotoArena Toruń |
E793803
|
entity |
| Predicate | hasSafetyFencing |
P14204
|
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: [MotoArena Toruń, hasSafetyFencing, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSafetyFencing Context triple: [MotoArena Toruń, hasSafetyFencing, yes]
-
A.
hasSafetyInfrastructure
Indicates that appropriate safety-related structures, systems, or measures are present for the referenced entity or environment.
-
B.
closedForSafety
Indicates that an entity (such as a place, facility, or route) is temporarily unavailable or inaccessible due to safety concerns or hazards.
-
C.
hasSafeStandingAreas
Indicates that designated locations within an area provide secure, stable, and protected spots where individuals can safely stand.
-
D.
hasGuardBars
Indicates that one entity is equipped with or protected by guard bars installed on or around it.
-
E.
hasBorderWallOrFence
chosen
Indicates that a physical barrier such as a wall or fence exists along the border between two entities.
- 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 29, 2026, 9:06 p.m.