Triple
T345943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guam Legislature |
E6941
|
entity |
| Predicate | typeOfLawMade |
P2588
|
FINISHED |
| Object | territorial statutes |
—
|
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: territorial statutes | Statement: [Guam Legislature, typeOfLawMade, territorial statutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfLawMade Context triple: [Guam Legislature, typeOfLawMade, territorial statutes]
-
A.
typeOfLaw
Indicates that one entity is a specific category or kind of law to which the other entity pertains.
-
B.
branchOfLaw
Indicates a relationship where one legal field or discipline is a subdivision or specialized area within a broader body of law.
-
C.
typeOfLegislation
chosen
Indicates the specific category or kind of legislation that a given legal act or measure belongs to.
-
D.
legalDoctrine
Indicates that one legal principle, rule, or theory is being applied, referenced, or relied upon as an authoritative basis for interpreting or deciding a legal issue.
-
E.
legalAct
Indicates that an entity performs, enacts, or is involved in a formal legal action, measure, or proceeding under a legal framework.
- 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eb0240e88190bc70784772f5fa30 |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e95451a4819090f4e4fb9b21a493 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.