Triple
T6777967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Farm Credit System |
E155605
|
entity |
| Predicate | isTaxExemptOn |
P72740
|
FINISHED |
| Object | certain securities |
—
|
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: certain securities | Statement: [Federal Farm Credit System, isTaxExemptOn, certain securities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTaxExemptOn Context triple: [Federal Farm Credit System, isTaxExemptOn, certain securities]
-
A.
isTaxable
Indicates that the subject is legally subject to taxation under the applicable tax rules or regulations.
-
B.
hasTaxPolicyResponsibility
Indicates that an entity holds authority or duty for creating, managing, or overseeing tax-related policies for another entity or jurisdiction.
-
C.
providesExemptionsTo
Indicates that one entity grants or offers exemptions, waivers, or exceptions from rules, obligations, or requirements to another entity.
-
D.
taxOn
Indicates that one entity imposes or applies a tax on another entity or item.
-
E.
hasOwnTaxSystem
Indicates that an entity maintains and administers its own distinct system of taxation, separate from other jurisdictions or authorities.
- F. None of above. chosen
Provenance (4 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_69c688162bf8819088b664b5c3b5be7a |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2689d408190bc2c1ce4ae9c1b13 |
completed | March 27, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69c6d095dcac8190bb9b943f50a7f885 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d182213c819086fcbbfd3d64d80b |
completed | March 27, 2026, 6:50 p.m. |
Created at: March 27, 2026, 2:13 p.m.