Triple
T21770131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panagia of Kykkos |
E537400
|
entity |
| Predicate | faceVisibility |
P145890
|
FINISHED |
| Object | faces traditionally kept hidden |
—
|
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: faces traditionally kept hidden | Statement: [Panagia of Kykkos, faceVisibility, faces traditionally kept hidden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: faceVisibility Context triple: [Panagia of Kykkos, faceVisibility, faces traditionally kept hidden]
-
A.
isOnFace
Indicates that one entity is located directly on the surface or face of another entity.
-
B.
hasFace
Indicates that one entity possesses, displays, or is characterized by a face.
-
C.
isFaceOn
Indicates that one surface or side of an object is oriented directly toward, or aligned to face, another object or reference direction.
-
D.
facesChallenge
Indicates that an entity is confronted with a difficulty, obstacle, or demanding situation that must be dealt with or overcome.
-
E.
faceValueType
Indicates the type or category of a financial instrument’s face (nominal) value, such as how that value is defined or represented.
- 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_69e0c46f5d1c8190bf830409e98464e5 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f031ad76848190b2c7a05d091b7faf |
completed | April 28, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69e6d054737081908aa7112975b77475 |
completed | April 21, 2026, 1:18 a.m. |
Created at: April 16, 2026, 6:51 p.m.