Triple
T2020506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FATCA Form 8938 |
E44092
|
entity |
| Predicate | hasInstructionDocument |
P28142
|
FINISHED |
| Object | Instructions for Form 8938 |
—
|
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: Instructions for Form 8938 | Statement: [FATCA Form 8938, hasInstructionDocument, Instructions for Form 8938]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInstructionDocument Context triple: [FATCA Form 8938, hasInstructionDocument, Instructions for Form 8938]
-
A.
hasOfficialDocument
Indicates that an entity possesses or is associated with a formal, authorized document issued by a recognized authority.
-
B.
hasLegalInstrument
Indicates that there exists a formal legal document or instrument that establishes, governs, or records the relationship between the related entities.
-
C.
hasIdentityDocument
Indicates that an entity possesses or is associated with a specific identity document.
-
D.
hasDocumentationAt
chosen
Indicates that something is documented or described in a specific document, file, or location.
-
E.
hasEthicsDocument
Indicates that an entity possesses or is associated with a formal document outlining ethical principles, guidelines, or policies.
- 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8d0bcbc8190bbbb726ecae1c51b |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb7a389408190a84a54856352f15b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.