Triple
T14030372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | golden ratio |
E337571
|
entity |
| Predicate | hasConjugateName |
P112548
|
FINISHED |
| Object | silver ratio (in some contexts) |
—
|
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: silver ratio (in some contexts) | Statement: [golden ratio, hasConjugateName, silver ratio (in some contexts)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConjugateName Context triple: [golden ratio, hasConjugateName, silver ratio (in some contexts)]
-
A.
hasConjugateField
Indicates that one field is the conjugate (typically complex-conjugate-related) counterpart of another field.
-
B.
hasConjugationOperation
Indicates that there exists an operation that transforms an entity into its conjugate form (e.g., algebraic, complex, or grammatical conjugation).
-
C.
hasConjunctForms
Indicates that an entity is associated with one or more conjunct (combined or compound) forms of itself or related elements.
-
D.
hasConjugateBase
Indicates that one chemical species is the conjugate base formed when another species donates a proton (H⁺).
-
E.
hasProperName
Indicates that an entity is associated with a specific proper name used to uniquely identify it.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2fa9f8248190930954d609dee5f1 |
completed | April 14, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69de05ab36b48190920efb1869bdb1fe |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:20 p.m.