Triple
T18302738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Connect America Fund |
E438394
|
entity |
| Predicate | technologyNeutral |
P7054
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Connect America Fund, technologyNeutral, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technologyNeutral Context triple: [Connect America Fund, technologyNeutral, true]
-
A.
technologyBasis
Indicates that one entity is founded on, enabled by, or fundamentally relies upon the technology provided or represented by another entity.
-
B.
technologyIncludes
Indicates that one technology encompasses, contains, or incorporates another technology as part of its components, features, or implementation.
-
C.
platformNeutral
chosen
Indicates that something is compatible with, applicable to, or designed to work across multiple platforms without dependence on any specific one.
-
D.
technologyType
Indicates the specific kind or category of technology associated with an entity or relationship.
-
E.
technologyDiscussed
Indicates that a conversation, text, or interaction includes discussion or mention of a particular technology.
- 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50180ac48819090e9a8f11ba10c3d |
completed | April 19, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:35 a.m.