Triple
T24281043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulju County |
E605539
|
entity |
| Predicate | hasPetroglyphSite |
P107795
|
FINISHED |
| Object | Daegokcheon Stream Petroglyphs |
—
|
NE NERFINISHED |
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: Daegokcheon Stream Petroglyphs | Statement: [Ulju County, hasPetroglyphSite, Daegokcheon Stream Petroglyphs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPetroglyphSite Context triple: [Ulju County, hasPetroglyphSite, Daegokcheon Stream Petroglyphs]
-
A.
hasRockArtSite
chosen
Indicates that an entity possesses, contains, or is associated with a rock art site.
-
B.
hasNearbyArchaeologicalSite
Indicates that an entity is located close to or in the vicinity of an archaeological site.
-
C.
numberOfPetroglyphs
Indicates the quantity of petroglyphs associated with a given subject or location.
-
D.
hasArchaeologicalSiteStatus
Indicates that an entity holds an officially recognized status or designation as an archaeological site.
-
E.
hasArchaeologicalSiteIn
Indicates that an entity possesses, contains, or is associated with an archaeological site located within a specified place or region.
- 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_69e295480d0c8190846fc3c2e2da1d4c |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f5227888190b1713af150fa30a1 |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:08 a.m.