Triple
T17906532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kevin |
E447715
|
entity |
| Predicate | oftenCallsEds |
P129247
|
FINISHED |
| Object | dorks |
—
|
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: dorks | Statement: [Kevin, oftenCallsEds, dorks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenCallsEds Context triple: [Kevin, oftenCallsEds, dorks]
-
A.
oftenSays
Indicates that one entity frequently makes a particular statement or remark, or regularly expresses a certain idea or phrase.
-
B.
oftenDedicatedTo
Indicates that something is frequently or habitually devoted, assigned, or committed to a particular purpose, activity, or recipient.
-
C.
oftenRefersTo
Indicates that one entity is frequently used to mention, denote, or reference another entity in common usage or context.
-
D.
oftenSoughtOn
Indicates that one entity is frequently searched for, requested, or pursued in relation to another entity.
-
E.
oftenHave
Indicates that one entity frequently possesses, experiences, or is associated with another entity.
- 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_69d8b9f6d394819082a6d69fd1e23d2f |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49e9c7f54819088c6d2ce7bbea073 |
completed | April 19, 2026, 9:21 a.m. |
| PD | Predicate disambiguation | batch_69e3d8ec2f6881909d7f54b878cbed37 |
completed | April 18, 2026, 7:18 p.m. |
| PDg | Predicate description generation | batch_69e3db77df0c819084548168c62b398c |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:19 a.m.