Triple
T20752268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Howard |
E510753
|
entity |
| Predicate | hasHumanNamePattern |
P60600
|
FINISHED |
| Object | English-language personal 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: English-language personal name | Statement: [George Howard, hasHumanNamePattern, English-language personal name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHumanNamePattern Context triple: [George Howard, hasHumanNamePattern, English-language personal name]
-
A.
namePattern
chosen
Indicates that an entity’s name follows or matches a specified pattern or format.
-
B.
hasSurnamePattern
Indicates that an entity’s surname follows or matches a specified structural or stylistic pattern.
-
C.
hasPattern
Indicates that one entity exhibits, follows, or is characterized by a specific recurring form, structure, or design defined by another entity.
-
D.
hasNameCharacteristic
Indicates that an entity possesses a specific quality or attribute related to its name.
-
E.
hasNaming
Indicates that one entity assigns, bears, or is associated with a specific name or designation provided by 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_69e0b4c909ec8190b05987f1639513f6 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c22be6588190b137193cb3184fc0 |
completed | April 21, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:34 p.m.