Triple
T17252949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marsi |
E418802
|
entity |
| Predicate | ethnicNameEtymology |
P64092
|
FINISHED |
| Object | possibly related to the god Mars |
—
|
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: possibly related to the god Mars | Statement: [Marsi, ethnicNameEtymology, possibly related to the god Mars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnicNameEtymology Context triple: [Marsi, ethnicNameEtymology, possibly related to the god Mars]
-
A.
nameEtymologyFor
Indicates that one entity expresses or explains the origin or derivation of the name of another entity.
-
B.
possibleNameEtymology
chosen
Indicates a hypothesized or suggested origin or derivation of an entity’s name from another term, source, or linguistic root.
-
C.
languageOfNamesake
Indicates the language in which the namesake of an entity (such as a person, place, or object) is named or expressed.
-
D.
hasEthnolinguisticOriginOfToponym
Indicates that a toponym (place name) originates from or is derived from a particular ethnolinguistic group or language.
-
E.
ethnonymAttestedIn
Indicates that the name of an ethnic group (ethnonym) is documented or recorded in a specified source, context, or medium.
- 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e6a1b648190a8bb2deb67bbdfdc |
completed | April 19, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.