Triple
T29401833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Timor Sea Designated Authority |
E745663
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | joint regulatory body |
C43630
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: joint regulatory body Context triple: [Timor Sea Designated Authority, instanceOf, joint regulatory body]
-
A.
financial regulatory coordination body
A financial regulatory coordination body is an organization that facilitates collaboration, information-sharing, and policy alignment among multiple financial regulators to promote consistent oversight, reduce systemic risk, and address cross-border or cross-sector regulatory issues.
-
B.
joint organization
chosen
A joint organization is a collaborative entity formed by two or more independent parties that share resources, responsibilities, and decision-making to achieve common objectives.
-
C.
governing body
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
D.
regulatory working group
A regulatory working group is a collaborative body of experts and stakeholders convened to analyze, develop, and recommend policies, standards, or compliance strategies within a specific regulatory domain.
-
E.
intergovernmental legal body
An intergovernmental legal body is an organization formed by multiple governments to develop, interpret, or oversee the implementation of international legal norms, agreements, and dispute-resolution mechanisms.
- F. None of above.
Provenance (1 batch)
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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 2:51 p.m.