Triple
T24857549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aleph (mathematics) |
E622067
|
entity |
| Predicate | alphabetOrigin |
P143350
|
FINISHED |
| Object | Hebrew letter aleph (ℵ) |
—
|
NE NERFINISHED |
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: Hebrew letter aleph (ℵ) | Statement: [Aleph (mathematics), alphabetOrigin, Hebrew letter aleph (ℵ)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alphabetOrigin Context triple: [Aleph (mathematics), alphabetOrigin, Hebrew letter aleph (ℵ)]
-
A.
hasLanguageOfOrigin
Indicates that one entity has its origin or source in the language specified by another entity.
-
B.
hasAcronymOrigin
Indicates that an acronym is derived from or originates from a specific longer expression or name.
-
C.
claimedOriginOfLanguage
Indicates that an entity asserts or is asserted to be the source or birthplace of a particular language.
-
D.
hasNameEtymologyIn
chosen
Indicates that the origin or derivation of an entity’s name is based in, or traceable to, a specified source such as a language, place, or cultural context.
-
E.
etymologyStatus
Indicates the status or reliability classification of an etymological explanation for a term or name.
- 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_69e2fac350d08190b3affde1b451a8c5 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:21 a.m.