Triple
T8262912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jones Law for Puerto Rico |
E193234
|
entity |
| Predicate | legalStatusOfCitizenship |
P50609
|
FINISHED |
| Object | statutory U.S. citizenship |
—
|
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: statutory U.S. citizenship | Statement: [Jones Law for Puerto Rico, legalStatusOfCitizenship, statutory U.S. citizenship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusOfCitizenship Context triple: [Jones Law for Puerto Rico, legalStatusOfCitizenship, statutory U.S. citizenship]
-
A.
definedCitizenship
Indicates that a formal citizenship status has been legally established or specified for an entity.
-
B.
citizenshipType
chosen
Indicates the specific legal category or status of an individual's citizenship in relation to a state or country.
-
C.
legalStatusInHomeland
Indicates the legal status or classification an entity holds within its country or place of origin.
-
D.
dualCitizenshipStatus
Indicates that an entity holds legal citizenship in two different countries simultaneously.
-
E.
mayHoldCitizenshipOf
Indicates that an entity is allowed or eligible to possess citizenship status of a specified country or jurisdiction.
- 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_69ca82e081d48190986beaa51f498ab9 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb793991b481908ad7221405e88ab7 |
completed | March 31, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69cb36b8707881909aca349230495a5a |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:49 p.m.