Triple
T32054010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monte Tiberio |
E818565
|
entity |
| Predicate | hasOriginalFunctionOfRuins |
P194907
|
FINISHED |
| Object | imperial palace |
—
|
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: imperial palace | Statement: [Monte Tiberio, hasOriginalFunctionOfRuins, imperial palace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalFunctionOfRuins Context triple: [Monte Tiberio, hasOriginalFunctionOfRuins, imperial palace]
-
A.
hasRuin
Indicates that one entity possesses, contains, or is associated with a ruin or ruined structure.
-
B.
hasRuinsOn
Indicates that one location or object contains or is the site of ruins situated upon it.
-
C.
hasRuinsSharedWith
Indicates that two or more entities share the same ruins or archaeological remains in common.
-
D.
hasNumberOfChurchRuins
Indicates the quantity of church ruins associated with a given entity.
-
E.
cityRuinsOf
Indicates that a city is located on or associated with the ruins of another, earlier city.
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 |
completed | May 8, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fd8d8a16f08190b9e880901bfa44fe |
completed | May 8, 2026, 7:15 a.m. |
| PDg | Predicate description generation | batch_69fd8e5e9ca48190890a2caddc1f9f5c |
completed | May 8, 2026, 7:18 a.m. |
Created at: May 1, 2026, 12:21 a.m.