Triple
T8209642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASL |
E191780
|
entity |
| Predicate | sanctioningRevoked |
P81505
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [NASL, sanctioningRevoked, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sanctioningRevoked Context triple: [NASL, sanctioningRevoked, 2018]
-
A.
revokedFrom
Indicates that a previously granted right, permission, or status has been withdrawn from a particular entity.
-
B.
sanction
Indicates the imposition of an official penalty or restrictive measure by an authority in response to certain actions or behaviors.
-
C.
isSanctionedBy
Indicates that an entity is subject to official penalties, restrictions, or punitive measures imposed by another authority or organization.
-
D.
consequenceOfRevocation
Indicates that something occurs as a direct result of a prior revocation event or decision.
-
E.
canBeRevoked
Indicates that a previously granted status, permission, or agreement is subject to being withdrawn or canceled.
- F. None of above. chosen
Provenance (4 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_69ca82c8c054819087fedd9a5436b8a3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb76dc784881908e1f63ac907cdd01 |
completed | March 31, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69cb36ad01ac81909609b15f6a6c8581 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb4ab5162c8190bddd696078689895 |
completed | March 31, 2026, 4:16 a.m. |
Created at: March 30, 2026, 5:44 p.m.