Triple
T9757330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | village courts of American Samoa |
E236584
|
entity |
| Predicate | typicalSanctions |
P18137
|
FINISHED |
| Object | fines |
—
|
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: fines | Statement: [village courts of American Samoa, typicalSanctions, fines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSanctions Context triple: [village courts of American Samoa, typicalSanctions, fines]
-
A.
coSanctions
Indicates that two or more entities jointly impose or support the same sanction or set of sanctions on a target.
-
B.
typeOfSanction
chosen
Indicates the specific category or kind of sanction that is applied in a given situation.
-
C.
coSanctionsWith
Indicates that two or more entities jointly impose, support, or participate in the same sanctions or sanctioning action.
-
D.
sanctionsMayInclude
Indicates that specified sanctions are permitted to contain or encompass certain listed measures, penalties, or restrictions.
-
E.
sanction
Indicates the imposition of an official penalty or restrictive measure by an authority in response to certain actions or behaviors.
- 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_69ca84d64f6c8190a4ed4e9f5936eda5 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda046a4048190a2c66321a9911817 |
completed | April 1, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69cd03d0772c8190bd1750cf1cfba309 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:24 p.m.