Triple
T8906494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seated jade Buddha |
E212072
|
entity |
| Predicate | carvingDetail |
P49005
|
FINISHED |
| Object | intricately carved |
—
|
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: intricately carved | Statement: [Seated jade Buddha, carvingDetail, intricately carved]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carvingDetail Context triple: [Seated jade Buddha, carvingDetail, intricately carved]
-
A.
hasCarving
chosen
Indicates that one entity features or contains a carved design, inscription, or sculpted detail that is associated with or applied to another entity.
-
B.
carvedOutOf
Indicates that one entity has been physically shaped, cut, or formed from the material of another entity.
-
C.
carvedBy
Indicates that one entity has been shaped, cut, or sculpted from a material by another entity through a carving process.
-
D.
carvedInto
Indicates that one entity has been shaped, cut, or sculpted so that it takes the form or likeness of another entity.
-
E.
carvingPeriod
Indicates the time span or historical period during which the carving activity or process took place.
- 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_69ca839255248190b43984294abd92ae |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc64c51d6c819098dc33a480dfd462 |
completed | April 1, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69cc5ecf55248190a29f00fbf99f13c4 |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:55 p.m.