Triple

T27173
Position Surface form Disambiguated ID Type / Status
Subject Guam E544 entity
Predicate usesLegalSystem P605 FINISHED
Object U.S.-based common law 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: U.S.-based common law | Statement: [Guam, usesLegalSystem, U.S.-based common law]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesLegalSystem
Context triple: [Guam, usesLegalSystem, U.S.-based common law]
  • A. legalSystem chosen
    Indicates the formal framework of laws, rules, and institutions that governs how legal matters are defined, interpreted, and enforced within a society or jurisdiction.
  • B. hasJurisdictionOver
    Indicates that one authority or governing body holds legal power or control to make and enforce decisions over another entity, area, or matter.
  • C. legalBasis
    Indicates the legal rule, authority, or justification under which an action, decision, or status is established or carried out.
  • D. legalRecognition
    Indicates that an authority formally acknowledges the validity, status, or rights associated with an entity, relationship, or action under the law.
  • E. legalForm
    Indicates the specific legal structure or organizational type under which an entity is formally constituted and recognized by law.
  • 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_69a243b4ac2c8190b93c303df797b7b2 completed Feb. 28, 2026, 1:24 a.m.
NER Named-entity recognition batch_69a247798a348190bb943d38300ae3ef completed Feb. 28, 2026, 1:40 a.m.
PD Predicate disambiguation batch_69a24658749881909117b007ec3d8633 completed Feb. 28, 2026, 1:35 a.m.
Created at: Feb. 28, 2026, 1:34 a.m.