Triple
T28408302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kolona |
E719597
|
entity |
| Predicate | hasBuildingRemains |
P163458
|
FINISHED |
| Object | temple platform |
—
|
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: temple platform | Statement: [Kolona, hasBuildingRemains, temple platform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuildingRemains Context triple: [Kolona, hasBuildingRemains, temple platform]
-
A.
hasFormerBuilding
Indicates that an entity previously occupied or used a different building, which is identified as its former building.
-
B.
hasCastleRemains
Indicates that one entity possesses or contains the remaining structures or ruins of a castle associated with it.
-
C.
hasRuinsOn
chosen
Indicates that one location or object contains or is the site of ruins situated upon it.
-
D.
housesRemainsOf
Indicates that one entity serves as the location or container in which the physical remains of another entity are kept or preserved.
-
E.
hasBuriedRemains
Indicates that one entity contains or is the location of the buried remains of another entity.
- 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 28, 2026, 1:25 a.m.