Triple
T13275928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HEBREW LETTER FINAL PE |
E316188
|
entity |
| Predicate | nonFinalForm |
P109282
|
FINISHED |
| Object | HEBREW LETTER PE |
—
|
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: HEBREW LETTER PE | Statement: [HEBREW LETTER FINAL PE, nonFinalForm, HEBREW LETTER PE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonFinalForm Context triple: [HEBREW LETTER FINAL PE, nonFinalForm, HEBREW LETTER PE]
-
A.
nativeForm
Indicates that one entity is the original or native linguistic form of another, such as a word’s form in its source language.
-
B.
nonPostNominal
Indicates that the related element does not appear in a post-nominal position (i.e., it does not follow the noun it modifies or relates to).
-
C.
finaleForm
Indicates that one entity represents the final or ultimate form, version, or stage of another entity.
-
D.
ultimatelyDoesNot
Indicates that, despite any preceding conditions or possibilities, the referenced entity or action does not in the end occur, hold, or get carried out.
-
E.
nonVolatile
Indicates that the associated entity or state does not change, disappear, or lose its value when power is removed or over time.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69d99cf7f9c48190a6a4f452b4a2aefa |
completed | April 11, 2026, 12:59 a.m. |
Created at: April 9, 2026, 9:26 p.m.