Triple
T10626964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vili |
E250348
|
entity |
| Predicate | anthropogonicAct |
P9769
|
FINISHED |
| Object | gave humans understanding or mind |
—
|
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: gave humans understanding or mind | Statement: [Vili, anthropogonicAct, gave humans understanding or mind]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: anthropogonicAct Context triple: [Vili, anthropogonicAct, gave humans understanding or mind]
-
A.
actsOn
chosen
Indicates that one entity performs an action that affects, targets, or is directed toward another entity.
-
B.
fromAct
Indicates that an entity originates from, is produced by, or results from a specified action or event.
-
C.
managedAct
Indicates that one entity oversaw, directed, or was responsible for carrying out a particular action or activity.
-
D.
positionOnHumanActs
Indicates a stance, opinion, or policy that an entity holds regarding actions or behaviors performed by humans.
-
E.
governingBodyAction
Indicates an action, decision, or intervention carried out by a governing body in the exercise of its authority or responsibilities.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df8207f08190a6362a8ba00988b2 |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7fae088190973f70c69738af49 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 8:55 p.m.