Triple
T19176078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jok |
E469439
|
entity |
| Predicate | mayFunctionAs |
P14773
|
FINISHED |
| Object | given name nickname |
—
|
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: given name nickname | Statement: [Jok, mayFunctionAs, given name nickname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayFunctionAs Context triple: [Jok, mayFunctionAs, given name nickname]
-
A.
possibleFunction
chosen
Indicates that an entity may serve, or is capable of serving, a particular function or role, without asserting that it actually does so.
-
B.
mayActThrough
Indicates that an entity can exert influence, perform an action, or have an effect by means of another entity, mechanism, or intermediary.
-
C.
mayAlsoBeCalled
Indicates that one entity can alternatively be referred to by another name or label.
-
D.
mayCast
Indicates that an entity has the permission or ability to perform a casting action on another entity or resource.
-
E.
mayPass
Indicates that one entity is permitted or authorized to move through, cross, or gain access to another entity or location.
- 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f6181f0c8190b344072db0b7abbb |
completed | April 20, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.