Triple
T2830767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thracian Tomb of Sveshtari |
E62228
|
entity |
| Predicate | subterranean |
P42731
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Thracian Tomb of Sveshtari, subterranean, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subterranean Context triple: [Thracian Tomb of Sveshtari, subterranean, true]
-
A.
undergroundBranch
Indicates that one entity is a branch or extension of another that operates or exists in a hidden, secret, or non-public manner.
-
B.
buriedUnder
Indicates that one entity is located beneath another entity in such a way that it is covered or concealed by it, as if buried.
-
C.
submerged
Indicates that one entity is located beneath the surface of a liquid or other surrounding medium, typically fully covered by it.
-
D.
hasUndergroundMine
Indicates that one entity possesses, controls, or contains an underground mine associated with it.
-
E.
subductsBeneath
Indicates that one entity moves downward and underneath another, typically as part of a convergent or overriding interaction.
- 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_69ab4c3c39188190955b9c49d98463d8 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdebd5a2c81908f0e30a0ae0eb8df |
completed | March 7, 2026, 8:15 a.m. |
| PD | Predicate disambiguation | batch_69abdd0acab881909e8c25cbef83678c |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abddccd50c8190a975942f46cfc01f |
completed | March 7, 2026, 8:11 a.m. |
Created at: March 6, 2026, 10:01 p.m.