Triple
T25204217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pordenone Calcio |
E631203
|
entity |
| Predicate | geographicAreaRepresented |
P127010
|
FINISHED |
| Object | Province of Pordenone |
—
|
NE NERFINISHED |
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: Province of Pordenone | Statement: [Pordenone Calcio, geographicAreaRepresented, Province of Pordenone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicAreaRepresented Context triple: [Pordenone Calcio, geographicAreaRepresented, Province of Pordenone]
-
A.
geographicAreaOfSupport
Indicates the geographic region or area within which support, assistance, or services are provided or applicable.
-
B.
typeOfAreaRepresented
Indicates that one entity specifies the kind or category of area that another entity represents.
-
C.
politicalRegionRepresented
Indicates that one entity serves as the official political representative or governing body for a specified geographic or administrative region.
-
D.
represented region
Indicates that one entity serves as a symbolic or formal depiction of a specific geographic or spatial area.
-
E.
primaryRegionRepresented
chosen
Indicates the main geographic or administrative region that an entity officially represents or speaks for.
- 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f474baf50c81909ef63b5ec7d42bfd |
completed | May 1, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 12:52 p.m.