Triple
T30167402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aemilia region |
E766831
|
entity |
| Predicate | laterCorrespondsTo |
P198080
|
FINISHED |
| Object | Emilia (Italy) |
—
|
NE NERFINISHED |
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: Emilia (Italy) | Statement: [Aemilia region, laterCorrespondsTo, Emilia (Italy)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterCorrespondsTo Context triple: [Aemilia region, laterCorrespondsTo, Emilia (Italy)]
-
A.
laterBasedOn
Indicates that one event, state, or version occurs or is established after another, using the earlier one as its basis or reference point.
-
B.
arisesAfter
Indicates that one event, state, or condition comes into existence or begins only after another specified event, state, or condition has occurred.
-
C.
laterComplementedBy
Indicates that an earlier entity is subsequently supplemented, enhanced, or completed by a later entity.
-
D.
laterWithin
Indicates that one event or time point occurs later than another while still falling within a specified temporal interval or boundary.
-
E.
locatedAfter
Indicates that one entity is positioned later than another along a defined sequence, order, or spatial/temporal axis.
- F. None of above. chosen
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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fec8aef1d8819094c7fd7074038e6b |
completed | May 9, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69fec639876481908efd84a3631a4271 |
completed | May 9, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69fec8adaa308190a9a276f8c36f15f0 |
completed | May 9, 2026, 5:39 a.m. |
Created at: April 29, 2026, 7:23 p.m.