Triple
T20355745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italus |
E496640
|
entity |
| Predicate | historicExistence |
P16606
|
FINISHED |
| Object | uncertain |
—
|
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: uncertain | Statement: [Italus, historicExistence, uncertain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicExistence Context triple: [Italus, historicExistence, uncertain]
-
A.
historicalExistence
chosen
Indicates that an entity actually existed at some point in real-world history, as opposed to being fictional, hypothetical, or mythological.
-
B.
historicFor
Indicates that something holds historical significance or importance specifically in relation to another entity.
-
C.
historicSeeOf
Indicates that a place serves or has served as the principal episcopal seat or central ecclesiastical jurisdiction of a bishop or similar religious authority.
-
D.
historicCore
Indicates that something is part of, located within, or associated with the original historic center or oldest developed area of a place.
-
E.
historicUsePersistsIn
Indicates that a practice, feature, or condition originating in the past continues to exist or be applied in the present.
- 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_69e0b4a3f7f48190b37f354574028ca6 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67853f10881908ecde94036804a8a |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:25 a.m.