Triple
T28003269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BREN-don |
E707201
|
entity |
| Predicate | appliesToNameType |
P96685
|
FINISHED |
| Object | masculine given name "Brendon" |
—
|
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: masculine given name "Brendon" | Statement: [BREN-don, appliesToNameType, masculine given name "Brendon"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToNameType Context triple: [BREN-don, appliesToNameType, masculine given name "Brendon"]
-
A.
nameAppliesTo
Indicates that a particular name is assigned to, or valid for use with, a specific entity.
-
B.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
C.
supportsNameType
chosen
Indicates that one entity is capable of handling, recognizing, or being associated with a particular type or category of name.
-
D.
appliesToPropertyType
Indicates that something (such as a rule, constraint, or operation) is relevant to or valid for a specific type of property.
-
E.
appliesToServiceType
Indicates that something is relevant or applicable specifically to a particular type or category of service.
- 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_69ef96b980d88190a753b2f9a978595a |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: April 27, 2026, 7:58 p.m.