Triple
T17527486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gem City |
E426836
|
entity |
| Predicate | hasEtymologyConcept |
P127807
|
FINISHED |
| Object | comparison of Quincy to a gem |
—
|
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: comparison of Quincy to a gem | Statement: [Gem City, hasEtymologyConcept, comparison of Quincy to a gem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEtymologyConcept Context triple: [Gem City, hasEtymologyConcept, comparison of Quincy to a gem]
-
A.
hasEtymologyDetail
Indicates a relationship where additional explanatory or contextual information about the origin or derivation of a term is provided.
-
B.
hasEtymologicalBasis
Indicates that one term, name, or expression is derived from, based on, or historically formed from the other in terms of linguistic origin.
-
C.
etymologyStatus
Indicates the status or reliability classification of an etymological explanation for a term or name.
-
D.
etymologyType
Indicates the specific kind or category of etymological relationship that links a term to its linguistic origin or source.
-
E.
etymology
Indicates the historical origin and development of a word or term, including its source language and form.
- F. None of above. chosen
Provenance (4 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_69d889de677081909b22d2657b1f0292 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452d7523c819099278507e4a718d4 |
completed | April 19, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f8b9888190aa8a45e09acf4319 |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb37d148190b7f38599c06594ee |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:49 a.m.