Triple
T10853274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Watson-Wentworth |
E256204
|
entity |
| Predicate | hasDoubleBarrelledSurname |
P69803
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Watson-Wentworth, hasDoubleBarrelledSurname, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDoubleBarrelledSurname Context triple: [Watson-Wentworth, hasDoubleBarrelledSurname, true]
-
A.
isCompoundSurname
chosen
Indicates that a surname consists of two or more distinct name elements combined into a single family name.
-
B.
hasMarriedSurname
Indicates that a person’s current surname is the one they adopted through marriage.
-
C.
hasBaseSurname
Indicates that an entity’s surname is derived from, or fundamentally corresponds to, a specified base or canonical surname.
-
D.
hasExampleSurname
Indicates that an entity is associated with a sample or illustrative surname used as an example rather than a real or primary family name.
-
E.
hasComponentSurname
Indicates that an entity’s full name includes a specified surname as one of its component parts.
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75134299481909459fd87917261a7 |
completed | April 9, 2026, 7:11 a.m. |
| PD | Predicate disambiguation | batch_69d70d2b51448190bae748ed6c23edde |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:20 p.m.