Triple
T26951967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of the Jaguars |
E678798
|
entity |
| Predicate | hasCarvingSubject |
P48945
|
FINISHED |
| Object | jaguars |
—
|
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: jaguars | Statement: [Temple of the Jaguars, hasCarvingSubject, jaguars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCarvingSubject Context triple: [Temple of the Jaguars, hasCarvingSubject, jaguars]
-
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.
hasCarvingType
Indicates that one entity is associated with a specific type or style of carving applied to it.
-
C.
hasCarvings
chosen
Indicates that one entity features or contains carved designs or engravings on its surface, created by another entity or process.
-
D.
isCarvedWith
Indicates that one entity has been shaped, decorated, or formed by carving using another entity as the tool, method, or material.
-
E.
hasRootCarvings
Indicates that an object, typically a plant or tree, possesses carvings or engraved markings on its roots.
- 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_69eeeb4e75f08190b14fc91ca4a91488 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 27, 2026, 6:25 a.m.