Triple
T5561772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Entity List |
E145781
|
entity |
| Predicate | includesInformation |
P1393
|
FINISHED |
| Object | names of listed entities |
—
|
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: names of listed entities | Statement: [U.S. Entity List, includesInformation, names of listed entities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesInformation Context triple: [U.S. Entity List, includesInformation, names of listed entities]
-
A.
providesInformationIn
Indicates that one entity supplies or conveys information within or through another entity or context.
-
B.
requiredInformation
Indicates that certain data or details are necessary and must be provided for a process, action, or relationship to proceed or be valid.
-
C.
includes
chosen
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
D.
collectsInformationOn
Indicates that one entity gathers or acquires data, facts, or details about another entity.
-
E.
reasoningIncludes
Indicates that a reasoning process or argument explicitly incorporates or makes use of the referenced element as one of its components or steps.
- 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_69c008fdae24819081aa002ad99cd966 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02019c6748190aeefb86f489f726a |
completed | March 22, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69c01b10bbf8819098655839c03b7832 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.