Triple
T26197939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juan |
E655157
|
entity |
| Predicate | ultimatelyDerivedFromLanguage |
P61389
|
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: [Juan, ultimatelyDerivedFromLanguage, Hebrew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ultimatelyDerivedFromLanguage Context triple: [Juan, ultimatelyDerivedFromLanguage, Hebrew]
-
A.
derivedFromLanguageFamily
Indicates that one language originates from, or historically descends from, a particular language family.
-
B.
derivationLanguage
chosen
Indicates the language from which something (such as a word, term, or expression) is derived.
-
C.
hasLanguageOfOrigin
Indicates that one entity has its origin or source in the language specified by another entity.
-
D.
hasLanguageFormOf
Indicates that one entity is a specific linguistic form, expression, or realization of the language used by another entity.
-
E.
hasSuperordinateLanguage
Indicates that one language serves as a higher-level, overarching, or more general language in relation to another language.
- 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60cd8c4608190bdf0cc6142264239 |
completed | May 2, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:47 p.m.