Triple
T31456669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toma |
E802468
|
entity |
| Predicate | originatingArea |
P410
|
FINISHED |
| Object | Alpine regions of Piedmont |
—
|
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: Alpine regions of Piedmont | Statement: [Toma, originatingArea, Alpine regions of Piedmont]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatingArea Context triple: [Toma, originatingArea, Alpine regions of Piedmont]
-
A.
administrativeRegionOfOrigin
Indicates the administrative region (such as a state, province, or similar division) from which an entity originates or is associated by origin.
-
B.
originatingParty
Indicates the party from which an action, communication, transaction, or event initially originates or is initiated.
-
C.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
-
D.
originatingCircuit
Indicates that one entity is the source or starting circuit from which another circuit or signal originates.
-
E.
sourceRegion
chosen
Indicates the geographic or spatial region from which something originates or is derived.
- 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_69f348c678ac81908a2e950867619061 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a00c59b03dc8190870f0dd24603a1ef |
completed | May 10, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_6a00c5178bc88190b2a0e03f38314035 |
completed | May 10, 2026, 5:49 p.m. |
Created at: April 30, 2026, 9:16 p.m.