Triple
T4000340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Whaling Commission |
E89398
|
entity |
| Predicate | policyOn |
P13641
|
FINISHED |
| Object | whale conservation |
—
|
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: whale conservation | Statement: [International Whaling Commission, policyOn, whale conservation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policyOn Context triple: [International Whaling Commission, policyOn, whale conservation]
-
A.
policyName
Indicates the specific name or title assigned to a policy associated with an entity.
-
B.
issuesPolicyOn
chosen
Indicates that an authority or organization formally creates, approves, or enacts a policy concerning a particular subject or domain.
-
C.
policyStance
Indicates the position or viewpoint an entity holds regarding a specific policy or set of policies.
-
D.
policyTool
Indicates that an entity is a tool, mechanism, or instrument used to design, implement, or enforce a policy.
-
E.
policyLevel
Indicates the degree or tier of strictness, scope, or priority associated with a given policy.
- 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_69aed9585e788190bec2d39deba3750f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefa8579288190940487ad07e38de0 |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8f89f2881909b0965419d15d46c |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:34 p.m.