Triple
T1728194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lydia |
E37545
|
entity |
| Predicate | nameMeaningTradition |
P24069
|
FINISHED |
| Object | woman from Lydia (the region) or Lydian woman |
—
|
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: woman from Lydia (the region) or Lydian woman | Statement: [Lydia, nameMeaningTradition, woman from Lydia (the region) or Lydian woman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameMeaningTradition Context triple: [Lydia, nameMeaningTradition, woman from Lydia (the region) or Lydian woman]
-
A.
currentNameMeaning
Indicates that the predicate expresses the meaning or significance of an entity’s current name.
-
B.
hasGivenNameMeaning
chosen
Indicates that a given name carries a particular meaning or semantic interpretation.
-
C.
meaningOfNativeName
Indicates that one entity specifies the semantic meaning or translation of another entity’s native-language name.
-
D.
etymologyPossibleMeaning
Indicates a possible or hypothesized meaning that an etymological analysis suggests for a word or term.
-
E.
nameMeaningInArabic
Indicates that the predicate specifies the meaning or interpretation of a name when expressed in the Arabic 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_69a8861acab88190bb43cde203429399 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aadb7bda1081908f2c41c520c9c55c |
completed | March 6, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69aa61c0a0288190bce9d60062a84b69 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.