Triple
T23352331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Urim |
E592948
|
entity |
| Predicate | pairedTermEtymologyProposedMeaning |
P14723
|
FINISHED |
| Object | perfections |
—
|
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: perfections | Statement: [Urim, pairedTermEtymologyProposedMeaning, perfections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pairedTermEtymologyProposedMeaning Context triple: [Urim, pairedTermEtymologyProposedMeaning, perfections]
-
A.
etymologyProposedBy
Indicates that a proposed origin or derivation of a word or term is attributed to a particular person or source.
-
B.
etymologicalRootMeaning
chosen
Indicates that one term’s meaning originates from or is derived from the historical or original meaning of another term.
-
C.
hasEtymologyConcept
Indicates that something derives its origin, form, or meaning from a particular etymological concept or source.
-
D.
etymologyGloss
Indicates that a term’s meaning is explained by a brief gloss specifically describing its etymological origin or source.
-
E.
etymologicalSource
Indicates that one term or name originates from, is derived from, or has its roots in another term or 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_69e25d24d2a4819092e6ede74c2a918d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19a14e04c81909c007b97cf5378b6 |
completed | April 29, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:20 p.m.