Triple
T26504122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puʻu Loa Petroglyphs |
E669498
|
entity |
| Predicate | hasApproximateNumberOfPetroglyphs |
P84691
|
FINISHED |
| Object | 23000 |
—
|
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: 23000 | Statement: [Puʻu Loa Petroglyphs, hasApproximateNumberOfPetroglyphs, 23000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateNumberOfPetroglyphs Context triple: [Puʻu Loa Petroglyphs, hasApproximateNumberOfPetroglyphs, 23000]
-
A.
numberOfPetroglyphs
chosen
Indicates the quantity of petroglyphs associated with a given subject or location.
-
B.
numberOfIndividualGeoglyphsApprox
Indicates an approximate count of distinct individual geoglyphs associated with a given subject.
-
C.
approximateLatestPetroglyphDate
Indicates the estimated most recent date at which the petroglyphs were created or modified.
-
D.
hasApproximateNumberOfPictographs
Indicates that an entity is associated with a quantity of pictographs that is not exact but estimated or approximate.
-
E.
hasRockCarvingsFrom
Indicates that something contains or features rock carvings that originate from a specified source, place, or period.
- 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 27, 2026, 1:15 a.m.