Triple
T9757338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | village courts of American Samoa |
E236584
|
entity |
| Predicate | disputeTypes |
P40419
|
FINISHED |
| Object | family disputes |
—
|
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: family disputes | Statement: [village courts of American Samoa, disputeTypes, family disputes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disputeTypes Context triple: [village courts of American Samoa, disputeTypes, family disputes]
-
A.
disputeInvolves
Indicates that a particular dispute includes or concerns the specified entities as participants or parties to the conflict.
-
B.
hasDisputeType
chosen
Indicates that an entity is associated with a particular category or type of dispute.
-
C.
disputeOrigin
Indicates that there is disagreement or uncertainty about the source, cause, or initial point of something.
-
D.
disputeKnownAs
Indicates that a particular dispute is also referred to by an alternative name or title.
-
E.
disputeNumber
Indicates the identifier or count associated with a specific dispute within a set of disputes.
- 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.