Triple
T31513436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terra di Lavoro |
E804002
|
entity |
| Predicate | wasProvinceUnder |
P67919
|
FINISHED |
| Object | Kingdom of Naples |
—
|
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: Kingdom of Naples | Statement: [Terra di Lavoro, wasProvinceUnder, Kingdom of Naples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasProvinceUnder Context triple: [Terra di Lavoro, wasProvinceUnder, Kingdom of Naples]
-
A.
hadProvince
chosen
Indicates that a governing entity possessed administrative control or jurisdiction over a specific province.
-
B.
formerProvince
Indicates that an entity was previously a province of another entity but no longer holds that administrative status.
-
C.
laterProvince
Indicates that one administrative region or province succeeds another in time, coming into existence or effect after the other.
-
D.
laterProvinceName
Indicates that an entity (such as a region or administrative unit) is known by a different province name at a later point in time.
-
E.
wasColoniaIn
Indicates that a place or settlement functioned as a Roman colonia within a specified larger territorial or administrative unit.
- 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_69f348ceb0a48190ae7feca263b6296c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 9:51 p.m.