Triple
T7600006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leonore Gewessler |
E179958
|
entity |
| Predicate | sectorManaged |
P78090
|
FINISHED |
| Object | climate action |
—
|
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: climate action | Statement: [Leonore Gewessler, sectorManaged, climate action]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectorManaged Context triple: [Leonore Gewessler, sectorManaged, climate action]
-
A.
divisionManaged
Indicates that one entity has managerial authority or oversight responsibility over a specific division of another entity or organization.
-
B.
managedIn
Indicates that one entity is administered, operated, or overseen within the scope, control, or jurisdiction of another entity.
-
C.
registryManaged
Indicates that an entity is controlled, maintained, or overseen by a central registry or registration authority.
-
D.
sectorProtected
Indicates that a particular sector or area is safeguarded from harm, access, or exploitation by some form of protection or regulation.
-
E.
eraManagedIn
Indicates that an entity (such as a project, resource, or process) was administered, controlled, or overseen during a specific time period or era.
- 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_69c69f3487ec8190bf7acdf2dd91e6d6 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9d7cb288190b40ff5c9a09297d9 |
completed | March 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e2e42c8190afc802c4796c9cc2 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f8184bb08190b2f70545a6aa277c |
completed | March 27, 2026, 9:35 p.m. |
Created at: March 27, 2026, 3:53 p.m.