Triple
T6159319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potter |
E137400
|
entity |
| Predicate | hasLexicalCategory |
P7162
|
FINISHED |
| Object | proper noun |
—
|
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: proper noun | Statement: [Potter, hasLexicalCategory, proper noun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLexicalCategory Context triple: [Potter, hasLexicalCategory, proper noun]
-
A.
hasLexicalInfluenceOn
Indicates that one linguistic element (such as a word, phrase, or lexicon) has affected or shaped the form, usage, or meaning of another linguistic element.
-
B.
hasPronounCategory
Indicates that an entity is associated with a specific category or type of pronoun (such as personal, possessive, reflexive, etc.).
-
C.
hasLinguisticFeature
chosen
Indicates that an entity possesses a particular linguistic property, trait, or characteristic.
-
D.
lexicalItem
Indicates that one entity is a word or vocabulary unit associated with, or used to express, another entity (such as a concept, meaning, or linguistic entry).
-
E.
morphologicalClass
Indicates the classification of an entity based on its morphological form or structural pattern.
- 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_69c008a54fc88190b6ce4416490ca79d |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d3445dc8190822954cee90f0dd7 |
completed | March 22, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69c055f5b81481908819515cdc334ae6 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:17 p.m.