Triple
T22942565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fibonacci retracement |
E569773
|
entity |
| Predicate | hasKeyRatio |
P27181
|
FINISHED |
| Object | 0.236 |
—
|
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: 0.236 | Statement: [Fibonacci retracement, hasKeyRatio, 0.236]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyRatio Context triple: [Fibonacci retracement, hasKeyRatio, 0.236]
-
A.
hasKeyAccord
Indicates that one entity possesses or defines the primary key or governing agreement that authorizes or controls another entity.
-
B.
hasKeyQuantity
chosen
Indicates that an entity is associated with a primary or defining quantity that characterizes or measures it.
-
C.
hasKeyMeasure
Indicates that one entity is the primary or defining metric, indicator, or quantitative measure used to assess or evaluate another entity.
-
D.
hasKeyDua
Indicates that one entity possesses or is associated with a specific secondary or backup key related to another entity.
-
E.
hasKeyPass
Indicates that an entity possesses or is granted a key-based pass that allows access or authorization to something.
- 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_69e24590862c8190858f180ad302adab |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1819a509481908a3662ef80f757c7 |
completed | April 29, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:45 p.m.