Triple
T24477199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea Fisheries Committees |
E617262
|
entity |
| Predicate | couldRegulate |
P29625
|
FINISHED |
| Object | gear types |
—
|
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: gear types | Statement: [Sea Fisheries Committees, couldRegulate, gear types]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: couldRegulate Context triple: [Sea Fisheries Committees, couldRegulate, gear types]
-
A.
allowsRegulationOf
chosen
Indicates that one entity grants the authority, means, or conditions for another entity to control, manage, or govern something.
-
B.
alsoRegulates
Indicates that an entity not only has a primary regulatory effect on a target but additionally regulates that same target through another, supplementary regulatory relationship.
-
C.
intendedToRegulate
Indicates that one entity is designed, purposed, or meant to control, guide, or constrain the behavior, operation, or effects of another entity.
-
D.
regulationAtIssue
Indicates that a specific regulation is the subject of concern, dispute, or analysis in the given context.
-
E.
supportsRegulation
Indicates that one entity endorses, backs, or advocates for the implementation or continuation of a specific regulation.
- 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_69e2d7f3ae788190b683394db15f220e |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29ed313a08190b745e89fe1c6cf55 |
completed | April 30, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:21 a.m.