Triple
T37269746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dunan |
E924479
|
entity |
| Predicate | extremePointRole |
P47428
|
FINISHED |
| Object | westernmost point of Japan |
—
|
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: westernmost point of Japan | Statement: [Dunan, extremePointRole, westernmost point of Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extremePointRole Context triple: [Dunan, extremePointRole, westernmost point of Japan]
-
A.
directionalExtreme
chosen
Indicates that one entity lies at or near the furthest extent or boundary in a specified direction relative to another entity.
-
B.
epsilonRole
Indicates a role or function that is minimal, negligible, or used as a placeholder within a relationship or structure.
-
C.
hasExtremePoint
Indicates that one entity possesses or includes another entity that is an extreme (e.g., maximum or minimum) point within its structure or boundary.
-
D.
antRole
Indicates that one entity has a specific role, function, or responsibility in relation to another entity.
-
E.
possibleRole
Indicates that an entity is capable of or eligible to serve in a particular role or function in a given context.
- 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_69f76eacdd8c819094080d3991e6d37c |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:15 p.m.