Triple
T20071944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muni |
E499758
|
entity |
| Predicate | etymologicalSense |
P14723
|
FINISHED |
| Object | one who is silent |
—
|
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: one who is silent | Statement: [Muni, etymologicalSense, one who is silent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: etymologicalSense Context triple: [Muni, etymologicalSense, one who is silent]
-
A.
etymologicalRootMeaning
chosen
Indicates that one term’s meaning originates from or is derived from the historical or original meaning of another term.
-
B.
etymologicalSource
Indicates that one term or name originates from, is derived from, or has its roots in another term or name.
-
C.
etymologicalField
Indicates that one term belongs to a particular semantic or conceptual domain relevant to its etymological origin or historical development.
-
D.
etymologicalNote
Indicates that there is a note explaining the origin, historical development, or source language of a term or name.
-
E.
etymologicalLanguage
Indicates the language from which a word or term is historically derived in its etymology.
- 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66438633481908710907c48806499 |
completed | April 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:40 p.m.