Triple
T19216955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Segitiga Terumbu Karang |
E480509
|
entity |
| Predicate | berbatasanDengan |
P224
|
FINISHED |
| Object | wilayah laut Australia di selatan |
—
|
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: wilayah laut Australia di selatan | Statement: [Segitiga Terumbu Karang, berbatasanDengan, wilayah laut Australia di selatan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: berbatasanDengan Context triple: [Segitiga Terumbu Karang, berbatasanDengan, wilayah laut Australia di selatan]
-
A.
borderedBy
chosen
Indicates that one entity shares a common boundary or edge with another entity.
-
B.
boundaryBetween
Indicates that something serves as a dividing line or limit separating two distinct regions, areas, or entities.
-
C.
borderWithin
Indicates that one region’s border lies entirely inside the boundary of another region.
-
D.
borderTypeWithIndonesia
Indicates the type or nature of the border that an entity shares with Indonesia.
-
E.
contrastedWithBoundary
Indicates a relationship where one entity is compared or set in opposition to a defining limit, edge, or boundary of another entity to highlight their differences.
- 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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fa3aff9c8190974363683b8246f5 |
completed | April 20, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69e4dcf22b3c8190bee02e3af946e114 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:23 p.m.