Triple
T35374758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shoemaker (namesake unknown) |
E1021874
|
entity |
| Predicate | hasUnknownFullIdentity |
P193086
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Shoemaker (namesake unknown), hasUnknownFullIdentity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnknownFullIdentity Context triple: [Shoemaker (namesake unknown), hasUnknownFullIdentity, true]
-
A.
hasUnknown
Indicates that an entity possesses or is associated with information, attributes, or values that are not known or not specified.
-
B.
hasHiddenIdentity
Indicates that an entity possesses a secret or concealed identity that is not known to others.
-
C.
hasUnknownGivenName
Indicates that the given (first) name of the entity is not known or not specified.
-
D.
hasNotableIdentity
Indicates that an entity is recognized for a specific, distinguished role, status, or identity that makes it notable.
-
E.
hasIdentity
Indicates that one entity is the same as, or is identified as, another specific entity or identifier.
- 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_69f76df000488190ab7c97f565677055 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69fd37b45b4481908b947b52fbcb7ade |
completed | May 8, 2026, 1:09 a.m. |
Created at: May 3, 2026, 4:03 p.m.