Triple
T2590360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alex Honnold |
E58105
|
entity |
| Predicate | focusOfOrganizationFounded |
P935
|
FINISHED |
| Object | solar energy access |
—
|
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: solar energy access | Statement: [Alex Honnold, focusOfOrganizationFounded, solar energy access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusOfOrganizationFounded Context triple: [Alex Honnold, focusOfOrganizationFounded, solar energy access]
-
A.
organizationFounded
Indicates that an organization was established or created at a specific point in time, often by a particular founder or founding entity.
-
B.
foundedOrganization
Indicates that an entity established or created an organization.
-
C.
organizationTypeFounded
Indicates the type or category of organization that was established or created in a founding event.
-
D.
foundedFrom
Indicates that an entity was established or originated starting from a particular source, place, or prior entity.
-
E.
foundedFor
chosen
Indicates that an entity was established or created specifically to serve, support, or benefit another entity or purpose.
- 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_69ab4ac019c8819094add11c46706e32 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd40075f08190b760cb41c1417169 |
completed | March 7, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69abd0d19308819089ee942513d567a4 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.