Triple
T1344001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antarctic Treaty |
E28527
|
entity |
| Predicate | reviewClause |
P18276
|
FINISHED |
| Object | may be reviewed after 30 years from entry into force |
—
|
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: may be reviewed after 30 years from entry into force | Statement: [Antarctic Treaty, reviewClause, may be reviewed after 30 years from entry into force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reviewClause Context triple: [Antarctic Treaty, reviewClause, may be reviewed after 30 years from entry into force]
-
A.
reviewedBy
Indicates that an item, work, or action has been examined and evaluated by a specific agent or reviewer.
-
B.
reviewAggregator
Indicates that an entity functions as a collector and summarizer of reviews or ratings about other entities.
-
C.
canReview
Indicates that one entity has the permission or ability to evaluate, assess, or provide feedback on another entity.
-
D.
reargued
Indicates that an argument, case, or issue was presented and debated again, typically after having been argued previously.
-
E.
revisionMechanism
chosen
Indicates the method or process by which something is updated, corrected, or modified over time.
- 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_69a49854eb3481908c7d56b2e449a290 |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c23b8a9081908b78405d4ef806af |
completed | March 1, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69a4bef3e8fc8190ac9a1ba9b5879483 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.