Triple
T13275963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HEBREW LETTER FINAL PE |
E316188
|
entity |
| Predicate | hasPositionalForm |
P91118
|
FINISHED |
| Object | final-only |
—
|
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: final-only | Statement: [HEBREW LETTER FINAL PE, hasPositionalForm, final-only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPositionalForm Context triple: [HEBREW LETTER FINAL PE, hasPositionalForm, final-only]
-
A.
hasPositionalCategory
chosen
Indicates that something is associated with a specific positional classification or category based on its location or arrangement.
-
B.
hasScalarForm
Indicates that something possesses or can be represented in a single-valued (scalar) form rather than as a vector, matrix, or more complex structure.
-
C.
isNonPositionalSince
Indicates that something has not depended on or been defined by positional context since a specified point in time.
-
D.
hasPositionsFor
Indicates that one entity offers or contains available roles, jobs, or positions for another entity.
-
E.
hasFullForm
Indicates that one entity is the complete, expanded, or unabbreviated form of another entity.
- 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.