Triple
T15837467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bahya ibn Paquda |
E384019
|
entity |
| Predicate | laterLanguageOfDissemination |
P119843
|
FINISHED |
| Object | Hebrew |
—
|
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 | Statement: [Bahya ibn Paquda, laterLanguageOfDissemination, Hebrew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterLanguageOfDissemination Context triple: [Bahya ibn Paquda, laterLanguageOfDissemination, Hebrew]
-
A.
languageOfTransmission
Indicates the language used to convey or transmit the content or information in a given communication or resource.
-
B.
laterOfficialLanguage
Indicates that one language became an official language of an entity at a later time than another language.
-
C.
isScheduledLanguageOf
Indicates that a particular language is officially planned or designated to be used for a specific event, program, or context.
-
D.
laterSecondaryLanguageOfAdministration
Indicates that one language served as a subsequent or later secondary language used for administrative purposes in relation to another language.
-
E.
languageOfPromulgation
Indicates the language in which a law, decree, or official act is formally issued or proclaimed.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e142e3d48c8190ad0d0af89d062101 |
completed | April 16, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69e007647f908190adb178c68c7bb7cf |
completed | April 15, 2026, 9:47 p.m. |
Created at: April 10, 2026, 4:49 a.m.