Triple
T7602374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bamuni Hills |
E180012
|
entity |
| Predicate | hasCarvingType |
P78124
|
FINISHED |
| Object | bas-relief |
—
|
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: bas-relief | Statement: [Bamuni Hills, hasCarvingType, bas-relief]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCarvingType Context triple: [Bamuni Hills, hasCarvingType, bas-relief]
-
A.
hasCarving
Indicates that one entity features or contains a carved design, inscription, or sculpted detail that is associated with or applied to another entity.
-
B.
hasCarvings
Indicates that one entity features or contains carved designs or engravings on its surface, created by another entity or process.
-
C.
hasFrontCarvings
Indicates that an object or structure features carvings or sculpted details on its front-facing surface.
-
D.
hasRootCarvings
Indicates that an object, typically a plant or tree, possesses carvings or engraved markings on its roots.
-
E.
hasBranchCarvings
Indicates that an entity (such as a tree or wooden object) possesses carvings or engravings specifically on its branches.
- 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_69c69f3567008190ab01d2ca7b53584a |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9f8e7848190b44d9c16b9c95d37 |
completed | March 27, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e485f88190910b39da52a955fe |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f8184bb08190b2f70545a6aa277c |
completed | March 27, 2026, 9:35 p.m. |
Created at: March 27, 2026, 3:54 p.m.