Triple
T17851855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leonard Weiss |
E445825
|
entity |
| Predicate | hasExistenceStatus |
P129409
|
FINISHED |
| Object | real person |
—
|
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: real person | Statement: [Leonard Weiss, hasExistenceStatus, real person]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExistenceStatus Context triple: [Leonard Weiss, hasExistenceStatus, real person]
-
A.
hasExistentiale
Indicates that an entity possesses or is associated with an existential characteristic, condition, or mode of being.
-
B.
hasExits
Indicates that an entity provides one or more ways out or routes leading from it to other locations or states.
-
C.
existsAs
Indicates that one entity has the same identity or manifestation as another, effectively asserting they are the same existing thing or state.
-
D.
hasStatusBasedOn
Indicates that an entity’s status is determined or derived from another condition, event, or entity.
-
E.
hasUniqueStatus
Indicates that an entity possesses a status or condition that is distinct and not shared with any other entity in the given context.
- 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_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. |
| PDg | Predicate description generation | batch_69e3f022ec448190a9bf191be1c5f570 |
completed | April 18, 2026, 8:57 p.m. |
Created at: April 10, 2026, 10:17 a.m.