Triple
T33839446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apennine Mountains (Moon) |
E867318
|
entity |
| Predicate | hasEponymLanguage |
P66093
|
FINISHED |
| Object | Latin |
—
|
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 | Statement: [Apennine Mountains (Moon), hasEponymLanguage, Latin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEponymLanguage Context triple: [Apennine Mountains (Moon), hasEponymLanguage, Latin]
-
A.
eponymLanguage
chosen
Indicates that a language is named after (is the eponym of) a particular person, place, or entity.
-
B.
hasEndonym
Indicates that an entity has a name or designation used by native speakers or within its own local language or community.
-
C.
hasEndonymLanguage
Indicates that the language specified is the one in which a name or term is expressed in its own native or local form.
-
D.
hasNamesakeLanguage
Indicates that an entity has a language named after it or sharing the same name as the entity.
-
E.
hasEponymCategory
Indicates that one entity serves as the namesake or eponym for the category or class represented by the other entity.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7004e55988190a2d35d4a95a34610 |
completed | May 3, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:47 a.m.