Triple
T7846155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Form W-3 |
E181926
|
entity |
| Predicate | submissionMedium |
P79332
|
FINISHED |
| Object | paper |
—
|
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: paper | Statement: [Form W-3, submissionMedium, paper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: submissionMedium Context triple: [Form W-3, submissionMedium, paper]
-
A.
submissionType
Indicates the specific category or format under which something is submitted (e.g., as a document, assignment, application, or other submission class).
-
B.
submissionBy
Indicates that one entity is the submitter or originator of a particular submission associated with another entity.
-
C.
submissionBasis
Indicates the basis, criteria, or grounds on which something is submitted or filed (e.g., a document, application, or claim).
-
D.
repositoryMedium
Indicates the physical or digital medium through which a repository stores, maintains, or provides access to its contents.
-
E.
subsequentMedium
Indicates that one medium or format follows another in a sequence, typically as a later or alternative form of the same content or communication.
- 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_69ca8285d6488190a95d4c02d7354b53 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb163f5da08190b7340ef4cc01cd19 |
completed | March 31, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69cae92180f88190ae3d44c3de7adc93 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7855a3c81908b9318f7186fc0c0 |
completed | March 30, 2026, 10:21 p.m. |
Created at: March 30, 2026, 4:49 p.m.