Triple
T5949550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyramid of Userkaf |
E132362
|
entity |
| Predicate | currentAppearance |
P311
|
FINISHED |
| Object | low mound of rubble |
—
|
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: low mound of rubble | Statement: [Pyramid of Userkaf, currentAppearance, low mound of rubble]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentAppearance Context triple: [Pyramid of Userkaf, currentAppearance, low mound of rubble]
-
A.
appearance
chosen
Indicates how something looks or seems to an observer, including its visible form, condition, or outward impression.
-
B.
hasCharacterAppearance
Indicates that a character appears or is visually represented within a given work, scene, or context.
-
C.
adaptationAppearance
Indicates that one entity appears or is depicted in an adaptation of another entity (such as a work being represented in a derived or reinterpreted version).
-
D.
returnAppearance
Indicates that one entity resumes or restores a previous visual form, style, or outward appearance of another entity or of itself.
-
E.
typicalAppearanceContext
Indicates the usual situation, setting, or context in which an entity most commonly appears or is typically encountered.
- 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_69c00869d3308190af89b2453e0f7546 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03ee10b308190afe38b904ae7c5f7 |
completed | March 22, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c0335806788190b6488ca8b73f7a63 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4:02 p.m.