Triple
T31699704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irpinia DOC |
E809017
|
entity |
| Predicate | establishedAsDOC |
P5762
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Irpinia DOC, establishedAsDOC, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsDOC Context triple: [Irpinia DOC, establishedAsDOC, 20th century]
-
A.
establishedAs
chosen
Indicates that one entity is formally created, designated, or recognized in a particular role, status, or identity as another entity.
-
B.
establishedTo
Indicates that one entity was created, founded, or set up for the purpose of serving, supporting, or enabling another entity.
-
C.
establishedFrom
Indicates that something was created, founded, or formed starting from a specified source, origin, or prior entity.
-
D.
DOCEstablished
Indicates that a document or organization was formally created, founded, or brought into official existence at a specific time or by a specific agent.
-
E.
establishedAt
Indicates the specific time or date at which something (such as an organization, system, or entity) was founded or brought into existence.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 30, 2026, 11:11 p.m.