Triple
T32004322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Consus |
E817218
|
entity |
| Predicate | etymologyProposedFrom |
P5801
|
FINISHED |
| Object | Latin condere (to store, to found) |
—
|
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: Latin condere (to store, to found) | Statement: [Consus, etymologyProposedFrom, Latin condere (to store, to found)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: etymologyProposedFrom Context triple: [Consus, etymologyProposedFrom, Latin condere (to store, to found)]
-
A.
etymologyProposedBy
Indicates that a proposed origin or derivation of a word or term is attributed to a particular person or source.
-
B.
etymologyStatus
Indicates the status or reliability classification of an etymological explanation for a term or name.
-
C.
etymologyType
Indicates the specific kind or category of etymological relationship that links a term to its linguistic origin or source.
-
D.
etymology
Indicates the historical origin and development of a word or term, including its source language and form.
-
E.
etymologicalSource
chosen
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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b3fef2308190840009a605f422f3 |
completed | May 3, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:14 a.m.