Triple
T14030418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | golden ratio |
E337571
|
entity |
| Predicate | isFixedPointOf |
P29145
|
FINISHED |
| Object | x ↦ 1 + 1/x |
—
|
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: x ↦ 1 + 1/x | Statement: [golden ratio, isFixedPointOf, x ↦ 1 + 1/x]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFixedPointOf Context triple: [golden ratio, isFixedPointOf, x ↦ 1 + 1/x]
-
A.
isFixedFieldOf
Indicates that one element is a fixed, non-variable field or attribute that belongs to and is structurally defined as part of another entity.
-
B.
invariantOf
chosen
Indicates that one element is an invariant (a property or quantity that remains unchanged) with respect to another element, system, or transformation.
-
C.
fixedBy
Indicates that one entity is repaired, corrected, or resolved through the action or intervention of another entity.
-
D.
isReferencePointFor
Indicates that one entity serves as a positional or conceptual basis used to locate, measure, or interpret another entity.
-
E.
hasFixedParityWith
Indicates that two entities share the same parity property (e.g., both even or both odd) and thus their parity remains consistently matched.
- 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_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. |
Created at: April 9, 2026, 10:20 p.m.