Triple
T32004305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Consus |
E817218
|
entity |
| Predicate | altarVisibility |
P173107
|
FINISHED |
| Object | buried most of the year |
—
|
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: buried most of the year | Statement: [Consus, altarVisibility, buried most of the year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: altarVisibility Context triple: [Consus, altarVisibility, buried most of the year]
-
A.
hasAltarLocation
Indicates that an altar is situated at or associated with a specific location.
-
B.
hasAltar
Indicates that one entity possesses, contains, or includes an altar as part of its features or components.
-
C.
isShowCave
Indicates that a cave or cavern is being displayed, revealed, or made visible within a given context or environment.
-
D.
altarName
Indicates that an entity has a specific name assigned to an altar.
-
E.
towerAccessibleTo
Indicates that a particular tower can be reached, entered, or used by a specified agent or group under given conditions.
- 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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b3fef2308190840009a605f422f3 |
completed | May 3, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b21da77081908c5c015c4606d344 |
completed | May 3, 2026, 2:25 a.m. |
Created at: May 1, 2026, 12:14 a.m.