Triple
T27920255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. presidential candidate |
E706185
|
entity |
| Predicate | filesWith |
P30230
|
FINISHED |
| Object | Federal Election Commission |
—
|
NE NERFINISHED |
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: Federal Election Commission | Statement: [U.S. presidential candidate, filesWith, Federal Election Commission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: filesWith Context triple: [U.S. presidential candidate, filesWith, Federal Election Commission]
-
A.
filesReport
Indicates that one entity submits or delivers an official report or document to another entity or authority.
-
B.
fileUnder
Indicates that one item is categorized, classified, or stored within a particular folder, category, or organizational grouping.
-
C.
libraryFile
Indicates that one entity is a file that is part of, stored in, or managed by a particular library.
-
D.
supportsMultipleFiles
Indicates that the subject is capable of handling, processing, or operating on more than one file at the same time.
-
E.
filedWith
chosen
Indicates that one entity has officially submitted or registered something (such as a document, complaint, or application) to another entity or authority.
- 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_69ef96b6cc808190aab19fb18b235f4b |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 6:56 p.m.