Triple
T34873652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Day |
E1005819
|
entity |
| Predicate | hasNameComponentRole |
P197529
|
FINISHED |
| Object | William is the first 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: William is the first name | Statement: [William Day, hasNameComponentRole, William is the first name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameComponentRole Context triple: [William Day, hasNameComponentRole, William is the first name]
-
A.
hasNamedForRole
Indicates that an entity has been given a specific name or label that corresponds to a particular role it plays.
-
B.
isComponentOfNameOf
Indicates that one entity is the name of a component or part belonging to another entity.
-
C.
hasComponentName
Indicates that an entity includes or is associated with a component identified by a specific name.
-
D.
hasNamesakeRoleFor
Indicates that one entity holds a role or position that is named after, or serves as a namesake for, another entity.
-
E.
hasNameBearerRole
chosen
Indicates that an entity holds or fulfills the role of bearing or carrying a particular name.
- 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_69f76dbde1c08190a24e7f9beb564c8d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff2636e2bc8190bba91eff91431c6e |
completed | May 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69ff25c65be48190868480d94e1c4e89 |
completed | May 9, 2026, 12:17 p.m. |
Created at: May 3, 2026, 4 p.m.