Triple
T9433144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louisiade Archipelago |
E227433
|
entity |
| Predicate | hasSeaArea |
P87476
|
FINISHED |
| Object | Coral reef systems |
—
|
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: Coral reef systems | Statement: [Louisiade Archipelago, hasSeaArea, Coral reef systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeaArea Context triple: [Louisiade Archipelago, hasSeaArea, Coral reef systems]
-
A.
appliesToSeaArea
Indicates that something (such as a rule, restriction, or designation) is relevant or valid within a specified sea area.
-
B.
hasNotableSea
Indicates that an entity is associated with or contains a sea that is considered notable or significant.
-
C.
seaAreaIncludes
chosen
Indicates that a given sea area geographically contains or encompasses another specified area or feature.
-
D.
hasOcean
Indicates that a geographic region, country, or landmass is bordered by or directly adjacent to a particular ocean.
-
E.
seaAreaCode
Indicates the specific coded maritime or sea area associated with or relevant to an entity.
- 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_69ca8437a7ac81908651de48f2d2141d |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd7e61a114819081fc4a2ad39c96ba |
completed | April 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69cca55548488190b171ae695a3212de |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:49 p.m.