Triple
T18288567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schrock carbene |
E438047
|
entity |
| Predicate | hasMetalCenterType |
P26314
|
FINISHED |
| Object | early transition metal |
—
|
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: early transition metal | Statement: [Schrock carbene, hasMetalCenterType, early transition metal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMetalCenterType Context triple: [Schrock carbene, hasMetalCenterType, early transition metal]
-
A.
hasCentralStoneType
Indicates that an item, typically a piece of jewelry, features a central stone of a specified type.
-
B.
associatedMetal
chosen
Indicates a relationship where one entity is linked or connected to a particular metal, such as by composition, usage, origin, or symbolic association.
-
C.
hasCenterType
Indicates that something is characterized by or assigned a specific type or category of center.
-
D.
isCenterless
Indicates that an entity lacks a central element, core component, or defined center in the relevant structure or context.
-
E.
mainMetalProduced
Indicates that a location, facility, or process primarily produces a particular metal as its main output.
- 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e500fc49b88190bd5b562e0a959e9d |
completed | April 19, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:35 a.m.