Triple
T16338388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SSC Bari |
E396732
|
entity |
| Predicate | hasGeographicIdentity |
P12355
|
FINISHED |
| Object | club of Apulia region |
—
|
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: club of Apulia region | Statement: [SSC Bari, hasGeographicIdentity, club of Apulia region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeographicIdentity Context triple: [SSC Bari, hasGeographicIdentity, club of Apulia region]
-
A.
hasGeographicType
Indicates that an entity is associated with or classified by a specific type or category of geographic feature or area.
-
B.
hasTypicalGeographicOrigin
Indicates that an entity is commonly or characteristically associated with originating from a particular geographic location.
-
C.
hasGeographicBasis
Indicates that something is grounded in, derived from, or defined by a particular geographic location or area.
-
D.
hasRegionalIdentity
chosen
Indicates that an entity possesses or is associated with a specific regional or local identity.
-
E.
isGeographicalEntity
Indicates that something exists as a distinct geographic feature, area, or place within physical space.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2c4e6338081908aa03ee3dcbe5f70 |
completed | April 17, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.