Triple
T25151815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altamura |
E630097
|
entity |
| Predicate | breadHasStatus |
P12717
|
FINISHED |
| Object | DOP-certified |
—
|
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: DOP-certified | Statement: [Altamura, breadHasStatus, DOP-certified]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breadHasStatus Context triple: [Altamura, breadHasStatus, DOP-certified]
-
A.
hasStatusLabel
chosen
Indicates that an entity is associated with a specific status expressed as a human-readable label.
-
B.
hadBoroughStatusFrom
Indicates that an entity held the legal or administrative status of a borough starting from a specified point in time.
-
C.
statusIncludes
Indicates that one entity’s status set contains or encompasses the status (or statuses) of another entity.
-
D.
hadBoroughStatus
Indicates that an entity previously possessed the official status or designation of a borough.
-
E.
isStatusOf
Indicates that a particular status or condition is assigned to, or characterizes, a specific entity.
- 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_69e2ff349e408190a6f4a5a66279f54d |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f46b8404a48190a654528935d0f07d |
completed | May 1, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:30 a.m.