Triple
T21962755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wentworthe |
E542374
|
entity |
| Predicate | hasNameClass |
P115320
|
FINISHED |
| Object | hereditary surname |
—
|
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: hereditary surname | Statement: [Wentworthe, hasNameClass, hereditary surname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameClass Context triple: [Wentworthe, hasNameClass, hereditary surname]
-
A.
hasNameCharacteristic
Indicates that an entity possesses a specific quality or attribute related to its name.
-
B.
hasNameFunction
Indicates that an entity is associated with a function whose purpose is to provide or determine its name.
-
C.
hasClassName
chosen
Indicates that an entity is associated with or identified by a specific class name in a classification or type system.
-
D.
hasNameElementType
Indicates that something includes a specific type or category of element within its name.
-
E.
hasTypeName
Indicates that an entity is associated with a specific type name used to classify or identify its kind.
- 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_69e0c47fab1081908dc74a6545dbb051 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f12458e4488190a04f8d3958854b49 |
completed | April 28, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 8:01 p.m.