Triple
T21431084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sumba |
E528683
|
entity |
| Predicate | hasNotableGeography |
P12436
|
FINISHED |
| Object | sea cliffs |
—
|
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: sea cliffs | Statement: [Sumba, hasNotableGeography, sea cliffs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableGeography Context triple: [Sumba, hasNotableGeography, sea cliffs]
-
A.
hasNotableScenicSpot
Indicates that an entity possesses or is associated with a particularly remarkable or well-known scenic location.
-
B.
hasGeographyCharacteristic
chosen
Indicates that an entity possesses a specific geographical feature, property, or attribute.
-
C.
hasNotableNatureArea
Indicates that an entity possesses or is associated with a significant or noteworthy natural area.
-
D.
hasNotableHillRange
Indicates that an entity possesses or is associated with a significant or well-known range of hills.
-
E.
hasNotableSettlementRegion
Indicates that an entity has a significant or well-known settlement located within a specified geographic 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_69e0c455f3688190810bc96365791b0f |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b3eb08988190b50eca911442de7c |
completed | April 22, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_69e61639ee288190889ffd500d1260f6 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:49 p.m.