Triple
T13275955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HEBREW LETTER FINAL PE |
E316188
|
entity |
| Predicate | isCased |
P2204
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [HEBREW LETTER FINAL PE, isCased, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCased Context triple: [HEBREW LETTER FINAL PE, isCased, false]
-
A.
hasCaseInflection
Indicates that a word or phrase changes form to reflect grammatical case (such as nominative, accusative, etc.) in a given language context.
-
B.
hasCase
Indicates that one entity is involved in, associated with, or characterized by a particular case, instance, or occurrence represented by another entity.
-
C.
letterCase
chosen
Indicates the relationship between a character or string and its typographical case (such as uppercase, lowercase, or mixed case).
-
D.
casingType
Indicates the specific kind or category of casing associated with or used by an entity.
-
E.
caseSensitivityVariant
Indicates that one string or textual form is a variant of another that differs only in letter casing (e.g., uppercase vs lowercase).
- 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_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. |
Created at: April 9, 2026, 9:26 p.m.