Triple
T17851851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leonard Weiss |
E445825
|
entity |
| Predicate | hasIdentityType |
P110243
|
FINISHED |
| Object | personal name identity |
—
|
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: personal name identity | Statement: [Leonard Weiss, hasIdentityType, personal name identity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIdentityType Context triple: [Leonard Weiss, hasIdentityType, personal name identity]
-
A.
hasIdentity
Indicates that one entity is the same as, or is identified as, another specific entity or identifier.
-
B.
hasIdentityComponent
Indicates that an entity includes or is associated with a specific component that contributes to or defines its identity.
-
C.
typeOfIdentity
chosen
Indicates the specific category or nature of identity that characterizes or defines an entity within a given context.
-
D.
hasIdentityStatus
Indicates that an entity is associated with a particular identity-related state or condition (such as confirmed, provisional, or unknown).
-
E.
hasDistinctIdentity
Indicates that an entity possesses its own unique, distinguishable identity separate from other entities.
- 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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48fff6c288190a2b5e60b66c03ddc |
completed | April 19, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:17 a.m.