Triple
T32030510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avenue of Sport Stars in Cetniewo |
E817943
|
entity |
| Predicate | hasPlaquesFor |
P10975
|
FINISHED |
| Object | Polish athletes |
—
|
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: Polish athletes | Statement: [Avenue of Sport Stars in Cetniewo, hasPlaquesFor, Polish athletes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlaquesFor Context triple: [Avenue of Sport Stars in Cetniewo, hasPlaquesFor, Polish athletes]
-
A.
hasNumberOfPlaques
Indicates the relationship that specifies how many plaques are associated with a given entity.
-
B.
hasPlaquePlacement
Indicates that a plaque has been positioned or installed at a specific location or on a particular object.
-
C.
hasPlaque
chosen
Indicates that an entity possesses or displays a plaque, such as a commemorative plate or a deposit on a surface.
-
D.
hasPlaqueText
Indicates that an entity bears or is associated with a specific textual inscription, such as the wording on a plaque or sign.
-
E.
hasPlate
Indicates that one entity possesses, is equipped with, or includes a plate as part of its attributes or components.
- 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 1, 2026, 12:18 a.m.