Triple
T13125738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gold |
E311837
|
entity |
| Predicate | etymologyOfSymbol |
P53707
|
FINISHED |
| Object | Au from Latin "aurum" |
—
|
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: Au from Latin "aurum" | Statement: [Gold, etymologyOfSymbol, Au from Latin "aurum"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: etymologyOfSymbol Context triple: [Gold, etymologyOfSymbol, Au from Latin "aurum"]
-
A.
etymologyType
Indicates the specific kind or category of etymological relationship that links a term to its linguistic origin or source.
-
B.
historicalOriginMeaning
Indicates that one entity explains the original historical source or derivational meaning of another entity.
-
C.
etymologyPossibleMeaning
Indicates a possible or hypothesized meaning that an etymological analysis suggests for a word or term.
-
D.
etymologyTheme
Indicates that something (such as a word, name, or term) has its origin, derivation, or linguistic history related to a particular theme, source, or conceptual basis.
-
E.
etymologyGloss
chosen
Indicates that a term’s meaning is explained by a brief gloss specifically describing its etymological origin or source.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9819946808190b41335fb1054accd |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98043a74c81908648e6cd0b4c7f71 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:07 p.m.