Triple
T31324958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Occitan (in Guardia Piemontese) |
E798857
|
entity |
| Predicate | originOfCommunity |
P55458
|
FINISHED |
| Object | Piedmont |
E28229
|
NE 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: Piedmont | Statement: [Occitan (in Guardia Piemontese), originOfCommunity, Piedmont]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originOfCommunity Context triple: [Occitan (in Guardia Piemontese), originOfCommunity, Piedmont]
-
A.
originCommunity
chosen
Indicates the community, group, or locality from which an entity originally comes or is derived.
-
B.
foundedCommunity
Indicates that an entity established or created a community, organization, or group.
-
C.
originOfSettlement
Indicates the place, source, or starting point from which a settlement was established or originated.
-
D.
traditionalCommunityOf
Indicates that one entity is the customary or historically rooted community associated with, originating from, or traditionally linked to another entity.
-
E.
foundersOrigin
Indicates that the relationship specifies the geographic or cultural origin of the founders of an entity.
- F. None of above.
Provenance (4 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_69f224e3238c8190b2291f50ea4962cd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a00b2b425a8819091ff65695e98c3af |
completed | May 10, 2026, 4:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2a1e18937081908e6b1465f8348963 |
completed | June 11, 2026, 2:31 a.m. |
| PD | Predicate disambiguation | batch_6a00b06efa248190b2d16b4889185119 |
completed | May 10, 2026, 4:21 p.m. |
Created at: April 29, 2026, 9:15 p.m.