Triple
T24278451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khao Phing Kan |
E605474
|
entity |
| Predicate | hasNearbyRockFormation |
P155643
|
FINISHED |
| Object | Ko Tapu |
—
|
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: Ko Tapu | Statement: [Khao Phing Kan, hasNearbyRockFormation, Ko Tapu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyRockFormation Context triple: [Khao Phing Kan, hasNearbyRockFormation, Ko Tapu]
-
A.
hasNearbyPromontory
Indicates that one geographic feature or location is situated close to a promontory or headland.
-
B.
hasNearbyCave
Indicates that one entity is located close to or in the vicinity of a cave associated with another entity.
-
C.
hasStateRockFormation
Indicates a relationship where a state is associated with or designated as having a particular rock formation.
-
D.
notableRockFormation
Indicates that one entity is a rock formation that is especially remarkable, distinctive, or well-known in relation to the other entity.
-
E.
geologicalFormation
Indicates that one entity is a geological structure or feature that characterizes or composes the physical makeup of another entity.
- F. None of above. chosen
Provenance (4 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f5032f48190a027e2d8b382ee79 |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f27a753ca8819095706970d368f762 |
completed | April 29, 2026, 9:39 p.m. |
Created at: April 18, 2026, 12:07 a.m.