Triple
T6353937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gili Islands |
E142942
|
entity |
| Predicate | hasRegulationConcern |
P31131
|
FINISHED |
| Object | coral reef protection |
—
|
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 protection | Statement: [Gili Islands, hasRegulationConcern, coral reef protection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegulationConcern Context triple: [Gili Islands, hasRegulationConcern, coral reef protection]
-
A.
hasRegulations
Indicates that one entity imposes, contains, or is associated with rules or regulatory requirements that govern the behavior or operation of another entity.
-
B.
regulationAtIssue
Indicates that a specific regulation is the subject of concern, dispute, or analysis in the given context.
-
C.
regulatoryIssues
chosen
Indicates that there are regulatory concerns, non-compliance, or potential violations associated with the related entity or activity.
-
D.
associatedWithRegulation
Indicates a relationship where something is linked to, governed by, or relevant to a specific regulation or regulatory framework.
-
E.
subjectToRegulation
Indicates that an entity is governed, constrained, or controlled by a specific rule, law, or regulatory framework.
- 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_69c008d6dcbc8190aa1c2f1fd8916b42 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c067e0cf1081908ee7e83b9dcf740e |
completed | March 22, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69c060ec091c8190912aac44e1b8b1c9 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:31 p.m.