Triple
T18350583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Josef K. |
E439656
|
entity |
| Predicate | fullNameRevealed |
P131468
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Josef K., fullNameRevealed, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullNameRevealed Context triple: [Josef K., fullNameRevealed, false]
-
A.
fullName
Indicates that an entity has a complete personal name, typically combining given name(s) and family name into a single string.
-
B.
realName
Indicates that one entity is the actual, full, or birth name of another entity, which may be known by an alias, nickname, or alternate identity.
-
C.
namesakeFullName
Indicates that one entity’s full name is used as the namesake or source of the name for another entity.
-
D.
typicalFullName
Indicates that the object is the standard or commonly used full name associated with the subject.
-
E.
givenName
Indicates the personal first name assigned to an individual.
- 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_69d8b918221c8190a9f7b563d64ac677 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e514f83b648190b473cf611851c666 |
completed | April 19, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69e44fe91bc08190906518e1b120fcf0 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e4561d665081908ec555344e76d82b |
completed | April 19, 2026, 4:12 a.m. |
Created at: April 10, 2026, 10:37 a.m.