Triple
T14529497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bobinôt |
E340865
|
entity |
| Predicate | familyNameStatus |
P114635
|
FINISHED |
| Object | single-name character |
—
|
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: single-name character | Statement: [Bobinôt, familyNameStatus, single-name character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyNameStatus Context triple: [Bobinôt, familyNameStatus, single-name character]
-
A.
familyNameIn
Indicates that an entity has a specified family name (surname) in a particular language or cultural context.
-
B.
familyNameRefersTo
Indicates that a specified family name designates or refers to a particular person, group, or lineage.
-
C.
macroFamilyStatus
Indicates the broad genealogical relationship between languages or language families at the macro-family level.
-
D.
familyNameCategory
Indicates that an entity is associated with a particular classification or grouping based on its family name.
-
E.
genealogicalStatus
Indicates the familial or ancestral relationship that one individual has to another within a genealogy.
- F. None of above. chosen
Provenance (4 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dea051bc608190ad4d516c5e7bca43 |
completed | April 14, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c518fc08190a6ce4d8be05c4c5d |
completed | April 14, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69de5fb5ac548190932f238e37271741 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:22 a.m.