Triple
T24181884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kobina |
E599446
|
entity |
| Predicate | assignedByCustom |
P155603
|
FINISHED |
| Object | day of birth |
—
|
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: day of birth | Statement: [Kobina, assignedByCustom, day of birth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assignedByCustom Context triple: [Kobina, assignedByCustom, day of birth]
-
A.
assignedTo
Indicates that responsibility for a task, item, or role has been designated to a specific entity.
-
B.
assignedToWorkBy
Indicates that one entity is designated or directed by another entity to perform a specific job, task, or role.
-
C.
assignedByAbbreviation
Indicates that an assignment or designation was made by an entity identified through a specific abbreviation.
-
D.
assignedUnder
Indicates that one entity has been given responsibility, duty, or authority to act within the scope, supervision, or framework defined by another entity.
-
E.
assignedInStandard
Indicates that something is allocated or designated within a defined standard, specification, or normative framework.
- 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_69e288cca05481908faeb1563711114a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f27a753ca8819095706970d368f762 |
completed | April 29, 2026, 9:39 p.m. |
Created at: April 17, 2026, 11:34 p.m.