Triple
T14803920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baldwyn |
E347980
|
entity |
| Predicate | usageAs |
P2529
|
FINISHED |
| Object | family 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: family name | Statement: [Baldwyn, usageAs, family name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usageAs Context triple: [Baldwyn, usageAs, family name]
-
A.
usageType
chosen
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
-
B.
usageAmong
Indicates how frequently or in what manner something is used within a particular group, context, or population.
-
C.
usagePattern
Indicates how something is typically used or the recurring manner in which it is employed or consumed.
-
D.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
E.
usageInstruction
Indicates that one entity provides guidance or directions on how to properly use, operate, or handle 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decf30d044819082ac038e06481aab |
completed | April 14, 2026, 11:35 p.m. |
| PD | Predicate disambiguation | batch_69de8c0ef8a4819092d84478b1f56db1 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:34 a.m.