Triple
T23269637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GALLEX |
E588251
|
entity |
| Predicate | productIsotope |
P151614
|
FINISHED |
| Object | germanium-71 |
—
|
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: germanium-71 | Statement: [GALLEX, productIsotope, germanium-71]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productIsotope Context triple: [GALLEX, productIsotope, germanium-71]
-
A.
productVariant
Indicates that one entity is a specific variant or version of a more general product entity.
-
B.
productWith
Indicates a relationship where one entity is associated with, contains, or is offered together with another entity as a product.
-
C.
productIndication
Indicates that a product is intended, approved, or used for a particular purpose, condition, or application.
-
D.
byProduct
Indicates that one entity is produced incidentally or as a secondary result of a process, activity, or creation involving another entity.
-
E.
productFor
Indicates that one entity is intended to be used by, with, or in relation to another entity as its product or offering.
- 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_69e25d148adc819088efbf42672604e9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1957324bc8190b8b53d4b18386151 |
completed | April 29, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d8770d081908897c28b04e5faea |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 17, 2026, 4:45 p.m.