Triple
T27495594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercury dime |
E694011
|
entity |
| Predicate | commonNameOrigin |
P77560
|
FINISHED |
| Object | resembles Roman god Mercury |
—
|
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: resembles Roman god Mercury | Statement: [Mercury dime, commonNameOrigin, resembles Roman god Mercury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonNameOrigin Context triple: [Mercury dime, commonNameOrigin, resembles Roman god Mercury]
-
A.
commonNameDerivedFrom
chosen
Indicates that the commonly used name of one entity originates from, or is derived based on, another entity.
-
B.
commonName
Indicates that one entity is the commonly used or vernacular name by which the other entity is known.
-
C.
commonNameOf
Indicates that one entity is the commonly used or popular name by which the other entity is known.
-
D.
commonNameGroup
Indicates that multiple entities share the same commonly used name or are grouped under a single common name.
-
E.
otherCommonName
Indicates that an entity is known by an additional, alternative common name besides its primary one.
- 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_69ef538370888190b1ddf53bb4831188 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 27, 2026, 1:08 p.m.