Triple
T23701242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Cave (Puerto Rico) |
E585600
|
entity |
| Predicate | hasPetroglyphType |
P78124
|
FINISHED |
| Object | anthropomorphic figures |
—
|
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: anthropomorphic figures | Statement: [Indian Cave (Puerto Rico), hasPetroglyphType, anthropomorphic figures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPetroglyphType Context triple: [Indian Cave (Puerto Rico), hasPetroglyphType, anthropomorphic figures]
-
A.
hasCarvingType
chosen
Indicates that one entity is associated with a specific type or style of carving applied to it.
-
B.
numberOfPetroglyphs
Indicates the quantity of petroglyphs associated with a given subject or location.
-
C.
hasSculptureType
Indicates that an entity is associated with a sculpture and specifies the type or category of that sculpture.
-
D.
hasPetrovType
Indicates that an entity (typically a spacetime or gravitational field) is classified as having a specific Petrov type in the Petrov classification of its Weyl tensor.
-
E.
hasPotteryType
Indicates that an entity is associated with or characterized by a specific type or category of pottery.
- 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_69e24904bd508190abfcb74855de2918 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b682df6881908fe71be9833d3a88 |
completed | April 29, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:53 p.m.