Triple
T31217296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ken |
E795904
|
entity |
| Predicate | lessCommonAs |
P144109
|
FINISHED |
| Object | middle name |
—
|
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: middle name | Statement: [Ken, lessCommonAs, middle name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lessCommonAs Context triple: [Ken, lessCommonAs, middle name]
-
A.
moreCommonAs
Indicates that one thing occurs or is observed more frequently in a specified role, form, or context than in another.
-
B.
lessCommonNameFor
chosen
Indicates that the subject is a less commonly used name or label for the same entity or concept as the object.
-
C.
isLessCommonThan
Indicates that one item occurs, appears, or is observed less frequently than another item.
-
D.
moreCommonFrom
Indicates that one entity occurs or appears more frequently originating from, or associated with, the source specified by the other entity than from alternative sources.
-
E.
lessOptimizedFor
Indicates that one entity is designed, configured, or adapted to perform a task or function with lower efficiency or effectiveness compared to another entity.
- 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c49a8888190ab9e0382cbc7be98 |
completed | May 3, 2026, 12:52 a.m. |
| PD | Predicate disambiguation | batch_69f696673214819094350e1d2648ef34 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:10 p.m.