Triple
T27707186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Form 8833 |
E698586
|
entity |
| Predicate | informationRequired |
P12650
|
FINISHED |
| Object | specific treaty article relied upon |
—
|
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: specific treaty article relied upon | Statement: [Form 8833, informationRequired, specific treaty article relied upon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: informationRequired Context triple: [Form 8833, informationRequired, specific treaty article relied upon]
-
A.
requiredInformation
chosen
Indicates that certain data or details are necessary and must be provided for a process, action, or relationship to proceed or be valid.
-
B.
communicationRequirement
Indicates that one entity is obligated or expected to communicate with another entity under specified conditions or for a particular purpose.
-
C.
providedInformationTo
Indicates that one entity has supplied or communicated information to another entity.
-
D.
providedInformationOn
Indicates that one entity supplied or communicated specific information or details to another entity.
-
E.
requiredToProvide
Indicates that one entity has an obligation or duty to supply or furnish something to another entity.
- 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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 3 p.m.