Triple
T26094671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Room 3 of Temple of the Murals |
E658228
|
entity |
| Predicate | hasWallPaintingsOn |
P167281
|
FINISHED |
| Object | north wall |
—
|
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: north wall | Statement: [Room 3 of Temple of the Murals, hasWallPaintingsOn, north wall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWallPaintingsOn Context triple: [Room 3 of Temple of the Murals, hasWallPaintingsOn, north wall]
-
A.
hasMuralsFrom
Indicates that a location or structure contains murals that originate from or were created in a specified place or time period.
-
B.
hasMuralsDepicting
Indicates that one entity contains or features murals that visually represent or portray another entity.
-
C.
hasWallPaintingStyle
Indicates that an entity features or is associated with a particular style or type of wall painting.
-
D.
hasRockCarvingsFrom
Indicates that something contains or features rock carvings that originate from a specified source, place, or period.
-
E.
wallPaintingsSubject
Indicates that the subject depicted or represented in a set of wall paintings is this entity.
- 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_69ee5bbfc4d08190a1b206d0ac3a1e8d |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 26, 2026, 7:50 p.m.