Triple
T4488382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darmstadt |
E107304
|
entity |
| Predicate | hasNamedAfterIt |
P63
|
FINISHED |
| Object | chemical element darmstadtium |
—
|
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: chemical element darmstadtium | Statement: [Darmstadt, hasNamedAfterIt, chemical element darmstadtium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNamedAfterIt Context triple: [Darmstadt, hasNamedAfterIt, chemical element darmstadtium]
-
A.
namedAfterSince
Indicates that one entity has borne the name of another entity starting from a specific point in time.
-
B.
namedAfter
chosen
Indicates that one entity has been given its name in honor of, or derived from, another entity.
-
C.
laterNamed
Indicates that an entity was given a new name at a later time, linking its original identity to its subsequent name.
-
D.
usedAfterNameOf
Indicates that something is used immediately following the mention or specification of a name.
-
E.
hasSymbolNamedAfter
Indicates that one entity has a symbol whose name is derived from or dedicated to another entity.
- 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_69bd43f84f788190a1383579c4a595be |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd556d29f08190bab1e872dd7e819f |
completed | March 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69bd5213e3d0819094b026989e686f01 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 12:59 p.m.