Triple
T16066566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omer |
E389746
|
entity |
| Predicate | meaningInArabicRelatedForm |
P121498
|
FINISHED |
| Object | long-lived |
—
|
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: long-lived | Statement: [Omer, meaningInArabicRelatedForm, long-lived]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meaningInArabicRelatedForm Context triple: [Omer, meaningInArabicRelatedForm, long-lived]
-
A.
cognateInArabic
Indicates that a given term has a corresponding cognate form in Arabic that is historically or linguistically related in origin or structure.
-
B.
hasMeaningInPersian
Indicates that something (such as a word, phrase, or symbol) possesses a specific meaning when interpreted in the Persian language.
-
C.
hebrewMeaning
Indicates that one entity specifies or provides the meaning or translation of another entity in the Hebrew language.
-
D.
etymologicalRootMeaning
Indicates that one term’s meaning originates from or is derived from the historical or original meaning of another term.
-
E.
meaningInFinnish
Indicates that one entity expresses the meaning or translation of another entity in the Finnish language.
- 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_69d86daf32ec8190a8c0466c8f49c3c0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e18272f2288190a17d45fb01cc2b07 |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e185879c10819080a18e24969b5a6d |
completed | April 17, 2026, 12:57 a.m. |
Created at: April 10, 2026, 4:57 a.m.