Triple
T24980824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bellerus |
E625161
|
entity |
| Predicate | nameEtymologicallyLinkedTo |
P108324
|
FINISHED |
| Object | Bellerium |
—
|
NE NERFINISHED |
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: Bellerium | Statement: [Bellerus, nameEtymologicallyLinkedTo, Bellerium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameEtymologicallyLinkedTo Context triple: [Bellerus, nameEtymologicallyLinkedTo, Bellerium]
-
A.
hasNameEtymologyIn
Indicates that the origin or derivation of an entity’s name is based in, or traceable to, a specified source such as a language, place, or cultural context.
-
B.
possibleNameEtymology
Indicates a hypothesized or suggested origin or derivation of an entity’s name from another term, source, or linguistic root.
-
C.
nameEtymologyFor
Indicates that one entity expresses or explains the origin or derivation of the name of another entity.
-
D.
etymologyRelatesTo
Indicates a relationship where one term’s origin, history, or derivation is connected to another linguistic form, word, or source.
-
E.
etymologicalRootName
chosen
Indicates that one name is derived from, or originates etymologically in, another name.
- 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:02 a.m.