Triple
T4076077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FBI special agents |
E86766
|
entity |
| Predicate | requiredCitizenship |
P40423
|
FINISHED |
| Object | United States 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: United States citizenship | Statement: [FBI special agents, requiredCitizenship, United States citizenship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredCitizenship Context triple: [FBI special agents, requiredCitizenship, United States citizenship]
-
A.
requiresCitizenship
chosen
Indicates that one entity can only obtain, access, or participate in another entity if it holds citizenship of a specified country or jurisdiction.
-
B.
definedCitizenship
Indicates that a formal citizenship status has been legally established or specified for an entity.
-
C.
hasCitizenshipRestriction
Indicates that there is a legal or policy-based limitation on who can obtain or hold citizenship in a given context.
-
D.
countryOfCitizenship
Indicates the country in which a person or entity holds legal citizenship.
-
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_69aed93ebe448190a1f1686e28740ac9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc4ba3f08190a6c6aaf6e9c99bd5 |
completed | March 9, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69aef9082c2081908474f082a49bebc8 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.