Triple
T11789481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Israeli lira |
E280352
|
entity |
| Predicate | subunitNameBeforeDecimalReform |
P40619
|
FINISHED |
| Object | pruta |
—
|
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: pruta | Statement: [Israeli lira, subunitNameBeforeDecimalReform, pruta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subunitNameBeforeDecimalReform Context triple: [Israeli lira, subunitNameBeforeDecimalReform, pruta]
-
A.
subunitNameMeaning
Indicates that a specific name expresses or conveys the meaning or significance of a subunit within a larger entity or structure.
-
B.
hasSubunitName
chosen
Indicates that an entity includes or is associated with a named subunit or component as part of its structure or organization.
-
C.
formerSubunit
Indicates that one entity was previously a subunit or subordinate part of another entity, but no longer holds that status.
-
D.
subunitType
Indicates that one entity is a specific kind or classification of subunit within the structure or composition of another entity.
-
E.
subunitSymbol
Indicates that one entity is the symbolic or abbreviated representation (symbol) of a subunit 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a587c2d881909297c3a6c7d26080 |
completed | April 10, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69d8a2491f048190853239bc05090bf4 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.