Triple
T38525071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | León |
E922604
|
entity |
| Predicate | originatesFromLexeme |
P99154
|
FINISHED |
| Object | Latin "leo" |
—
|
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: Latin "leo" | Statement: [León, originatesFromLexeme, Latin "leo"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatesFromLexeme Context triple: [León, originatesFromLexeme, Latin "leo"]
-
A.
derivedFromLexeme
chosen
Indicates that one linguistic form or expression originates from, or is morphologically or semantically based on, a particular lexeme.
-
B.
hasLexicalCategoryOfOrigin
Indicates that one entity originates from, or is derived based on, the lexical category (such as noun, verb, adjective, etc.) of another entity.
-
C.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
-
D.
hasLexicalInfluenceOn
Indicates that one linguistic element (such as a word, phrase, or lexicon) has affected or shaped the form, usage, or meaning of another linguistic element.
-
E.
hasLexicalInformation
Indicates that an entity is associated with specific lexical data, such as word forms, meanings, or other language-related information.
- 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_69f76ea5f5588190bd0b28c82e975640 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.